<?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>Comments on: Secure Password Scheme for Turbogears2 Application with repoze.who and bcrypt</title>
	<atom:link href="http://www.heikkitoivonen.net/blog/2009/12/01/secure-password-scheme-for-turbogears2-application-with-repoze-who-and-bcrypt/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.heikkitoivonen.net/blog/2009/12/01/secure-password-scheme-for-turbogears2-application-with-repoze-who-and-bcrypt/</link>
	<description>A Finn in Silicon Valley - Adventures in Technology</description>
	<lastBuildDate>Wed, 17 Aug 2011 08:58:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Aigars Mahinovs</title>
		<link>http://www.heikkitoivonen.net/blog/2009/12/01/secure-password-scheme-for-turbogears2-application-with-repoze-who-and-bcrypt/comment-page-1/#comment-18421</link>
		<dc:creator>Aigars Mahinovs</dc:creator>
		<pubDate>Sat, 05 Dec 2009 19:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.heikkitoivonen.net/blog/?p=985#comment-18421</guid>
		<description>Heh, I implemented a random-salted SHA256 password extension to the TG2.0 default scheme in like 4 lines added to the default code and with 2 more lines allowed usage of legacy MD5 random-salted passwords that most of our users still have in the database.

I think the new default code in TG2.1 should accept any of the old hash types that TG ever supported (and some other legacy types, like AD-hash or Linux crypt()) and have an option (turned-off by default, but prominent) that would replace the hash with the most secure type on next login of a user.</description>
		<content:encoded><![CDATA[<p>Heh, I implemented a random-salted SHA256 password extension to the TG2.0 default scheme in like 4 lines added to the default code and with 2 more lines allowed usage of legacy MD5 random-salted passwords that most of our users still have in the database.</p>
<p>I think the new default code in TG2.1 should accept any of the old hash types that TG ever supported (and some other legacy types, like AD-hash or Linux crypt()) and have an option (turned-off by default, but prominent) that would replace the hash with the most secure type on next login of a user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heikki Toivonen</title>
		<link>http://www.heikkitoivonen.net/blog/2009/12/01/secure-password-scheme-for-turbogears2-application-with-repoze-who-and-bcrypt/comment-page-1/#comment-18237</link>
		<dc:creator>Heikki Toivonen</dc:creator>
		<pubDate>Wed, 02 Dec 2009 17:14:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.heikkitoivonen.net/blog/?p=985#comment-18237</guid>
		<description>Thanks John and Daniel. I&#039;ll definitely be checking out bcryptor and cryptacular.</description>
		<content:encoded><![CDATA[<p>Thanks John and Daniel. I&#8217;ll definitely be checking out bcryptor and cryptacular.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Holth</title>
		<link>http://www.heikkitoivonen.net/blog/2009/12/01/secure-password-scheme-for-turbogears2-application-with-repoze-who-and-bcrypt/comment-page-1/#comment-18232</link>
		<dc:creator>Daniel Holth</dc:creator>
		<pubDate>Wed, 02 Dec 2009 15:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.heikkitoivonen.net/blog/?p=985#comment-18232</guid>
		<description>I wrote Cryptacular (http://pypi.python.org/pypi/cryptacular) after reading that rant. It uses ctypes to talk to a public-domain bcrypt implementation instead of the BSD-licensed implementation.

It&#039;s designed for people who may need to deal with many different hashing schemes with optional hash migration when a user authenticates against a legacy hash. You can start using good hashes in your application without having to delete all your old password hashes; they will simply be replaced as users log in.</description>
		<content:encoded><![CDATA[<p>I wrote Cryptacular (<a href="http://pypi.python.org/pypi/cryptacular" rel="nofollow">http://pypi.python.org/pypi/cryptacular</a>) after reading that rant. It uses ctypes to talk to a public-domain bcrypt implementation instead of the BSD-licensed implementation.</p>
<p>It&#8217;s designed for people who may need to deal with many different hashing schemes with optional hash migration when a user authenticates against a legacy hash. You can start using good hashes in your application without having to delete all your old password hashes; they will simply be replaced as users log in.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Secal</title>
		<link>http://www.heikkitoivonen.net/blog/2009/12/01/secure-password-scheme-for-turbogears2-application-with-repoze-who-and-bcrypt/comment-page-1/#comment-18206</link>
		<dc:creator>John Secal</dc:creator>
		<pubDate>Wed, 02 Dec 2009 07:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.heikkitoivonen.net/blog/?p=985#comment-18206</guid>
		<description>bcryptor [1] is a wrapper for bcrypt that provides a high level object oriented wrapper around bcrypt as well as low level bindings to the C library, so it&#039;s very fast.

And there is not problem to install from PyPi.

$ sudo easy_install bcryptor


[1] http://pypi.python.org/pypi/bcryptor/</description>
		<content:encoded><![CDATA[<p>bcryptor [1] is a wrapper for bcrypt that provides a high level object oriented wrapper around bcrypt as well as low level bindings to the C library, so it&#8217;s very fast.</p>
<p>And there is not problem to install from PyPi.</p>
<p>$ sudo easy_install bcryptor</p>
<p>[1] <a href="http://pypi.python.org/pypi/bcryptor/" rel="nofollow">http://pypi.python.org/pypi/bcryptor/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

