<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Kommentare zu: PHP: Easy to use and secure PHP hashing Class</title>
	<atom:link href="http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/feed" rel="self" type="application/rss+xml" />
	<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html</link>
	<description>Ich bin nicht verrückt, nur technisch begabt ...</description>
	<lastBuildDate>Mon, 30 Jan 2012 16:05:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Von: Julius</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-1413</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Mon, 01 Aug 2011 19:46:58 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-1413</guid>
		<description>There is no way to get the password from a hash.
Hashes just work the way Input (like a password) -hashing-&gt; Hash. Not the other way round.
Encryption can do Input -encrypting-&gt; Encrypted Input -decrypting-&gt; Input but that aint practical.

Sending plain passwords via Email is also a security risk. I would avoid that.
Best way for you should be sending a unique link that can only be used once for resetting a password on your website.

Regards, Julius</description>
		<content:encoded><![CDATA[<p>There is no way to get the password from a hash.<br />
Hashes just work the way Input (like a password) -hashing-&gt; Hash. Not the other way round.<br />
Encryption can do Input -encrypting-&gt; Encrypted Input -decrypting-&gt; Input but that aint practical.</p>
<p>Sending plain passwords via Email is also a security risk. I would avoid that.<br />
Best way for you should be sending a unique link that can only be used once for resetting a password on your website.</p>
<p>Regards, Julius</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Tazek</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-1412</link>
		<dc:creator>Tazek</dc:creator>
		<pubDate>Mon, 01 Aug 2011 18:29:35 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-1412</guid>
		<description>Hi Julius,

I have a question: I&#039;m using your class on my login system. This login system has a &quot;reset password&quot; page, which sends the password by e-mail. I&#039;d like to find someway to &quot;generate&quot; the password from the hash.

What&#039;s the easy way to do it?

Thanks!</description>
		<content:encoded><![CDATA[<p>Hi Julius,</p>
<p>I have a question: I'm using your class on my login system. This login system has a "reset password" page, which sends the password by e-mail. I'd like to find someway to "generate" the password from the hash.</p>
<p>What's the easy way to do it?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Julius</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-1411</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Mon, 01 Aug 2011 09:57:27 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-1411</guid>
		<description>Hi Tazek,
i think i should do da rewrite of that code and publish it on github.
But that has to wait for after exams.
Regards, Julius</description>
		<content:encoded><![CDATA[<p>Hi Tazek,<br />
i think i should do da rewrite of that code and publish it on github.<br />
But that has to wait for after exams.<br />
Regards, Julius</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Tazek</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-1410</link>
		<dc:creator>Tazek</dc:creator>
		<pubDate>Sun, 31 Jul 2011 15:54:57 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-1410</guid>
		<description>Hi,

Your class seems to be really useful.
Is it the latest version? How can I get further updates?

Thank you!

Best,
Tazek</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Your class seems to be really useful.<br />
Is it the latest version? How can I get further updates?</p>
<p>Thank you!</p>
<p>Best,<br />
Tazek</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: bucabay</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-498</link>
		<dc:creator>bucabay</dc:creator>
		<pubDate>Tue, 20 Oct 2009 23:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-498</guid>
		<description>I think you hit the nail on the head with this one. There is a lot of bad advice that is just followed blindly regarding hashing of passwords. Especially the common advice that double hashing is bad, when it is used in my applications: http://en.wikipedia.org/wiki/Key_strengthening

I like the global hash and custom hash function. You could however consider the global salt, and custom hashing function. 

Great work!</description>
		<content:encoded><![CDATA[<p>I think you hit the nail on the head with this one. There is a lot of bad advice that is just followed blindly regarding hashing of passwords. Especially the common advice that double hashing is bad, when it is used in my applications: <a href="http://en.wikipedia.org/wiki/Key_strengthening" rel="nofollow">http://en.wikipedia.org/wiki/Key_strengthening</a></p>
<p>I like the global hash and custom hash function. You could however consider the global salt, and custom hashing function. </p>
<p>Great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Dustin</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-472</link>
		<dc:creator>Dustin</dc:creator>
		<pubDate>Sat, 03 Oct 2009 17:59:46 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-472</guid>
		<description>Hey Julius,

I like the idea of a combination of global salting and per unit salting, as I can see it&#039;s obvious benefits.  The argument for storing a users salt with the salted hashes can still be considered a viable measure, since a hacker would still need to know the insert method the code uses to salt (i.e. is it inserted by str_split, is it before the pass, after? etc...)  as always security does also rely on the length of the values being passed to be hashed.  The only problem I can forsee with a global hash however is, if it is lost, the scheme is broken, so precautions would need to be implemented to keep that from happening.

Great class, and I do like that it slows down the hashing routine.

-Dustin</description>
		<content:encoded><![CDATA[<p>Hey Julius,</p>
<p>I like the idea of a combination of global salting and per unit salting, as I can see it's obvious benefits.  The argument for storing a users salt with the salted hashes can still be considered a viable measure, since a hacker would still need to know the insert method the code uses to salt (i.e. is it inserted by str_split, is it before the pass, after? etc...)  as always security does also rely on the length of the values being passed to be hashed.  The only problem I can forsee with a global hash however is, if it is lost, the scheme is broken, so precautions would need to be implemented to keep that from happening.</p>
<p>Great class, and I do like that it slows down the hashing routine.</p>
<p>-Dustin</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Julius</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-471</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Fri, 02 Oct 2009 07:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-471</guid>
		<description>The global Salt is only a method for advanced use of the class to make hashes fetched with SQL-Injection useless. So the idea is not broken by default.
Adding a encryption with a secret key is not different to the use of a global salt when using only hashing functions.</description>
		<content:encoded><![CDATA[<p>The global Salt is only a method for advanced use of the class to make hashes fetched with SQL-Injection useless. So the idea is not broken by default.<br />
Adding a encryption with a secret key is not different to the use of a global salt when using only hashing functions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: julianor</title>
		<link>http://juliusbeckmann.de/blog/easy-to-use-and-secure-php-hashing-class.html/comment-page-1#comment-470</link>
		<dc:creator>julianor</dc:creator>
		<pubDate>Thu, 01 Oct 2009 20:32:57 +0000</pubDate>
		<guid isPermaLink="false">http://juliusbeckmann.de/blog/?p=449#comment-470</guid>
		<description>The global salt idea is broken. Salts are to avoid the same password resulting in the same hash. To do what you are trying to do you could encrypt every password with a real block cipher and a secret key before hashing. But if the attacker can retrieve all the hashes and he can change any password, your secret key starts to be useless too :)</description>
		<content:encoded><![CDATA[<p>The global salt idea is broken. Salts are to avoid the same password resulting in the same hash. To do what you are trying to do you could encrypt every password with a real block cipher and a secret key before hashing. But if the attacker can retrieve all the hashes and he can change any password, your secret key starts to be useless too :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

