Am 02.01.2013 11:11, schrieb Antoine Pitrou:
>> PKCS #1 support should be implemented on top of OpenSSL or NaCl. I'm
>> planing to use OpenSSL as primary implementation and additional code
>> as fallback implementation of PBKDF2-HMAC-SHA-1, PBKDF2-HMAC-SHA-256
>> and PBKDF2-HMAC-SHA-512.
>
> Does
Le Wed, 02 Jan 2013 11:06:07 +0100,
Christian Heimes a écrit :
> Am 02.01.2013 10:49, schrieb Antoine Pitrou:
> > Le Wed, 2 Jan 2013 09:18:17 +0100,
> > Dirkjan Ochtman a écrit :
> >> On Wed, Jan 2, 2013 at 7:14 AM, Christian Heimes
> >> wrote:
> >>> The second PEP addresses key derivation func
Am 02.01.2013 10:49, schrieb Antoine Pitrou:
> Le Wed, 2 Jan 2013 09:18:17 +0100,
> Dirkjan Ochtman a écrit :
>> On Wed, Jan 2, 2013 at 7:14 AM, Christian Heimes
>> wrote:
>>> The second PEP addresses key derivation functions for secure
>>> password hashing. I like to add PBKDF2, bcrypt and scryp
Le Wed, 2 Jan 2013 09:18:17 +0100,
Dirkjan Ochtman a écrit :
> On Wed, Jan 2, 2013 at 7:14 AM, Christian Heimes
> wrote:
> > The second PEP addresses key derivation functions for secure
> > password hashing. I like to add PBKDF2, bcrypt and scrypt
> > facilities to the standard library.
>
> Hash
On Wed, Jan 2, 2013 at 7:14 AM, Christian Heimes wrote:
> The second PEP addresses key derivation functions for secure password
> hashing. I like to add PBKDF2, bcrypt and scrypt facilities to the
> standard library.
Hashing only? I was hoping you would also include PKCS1 RSA primitives.
Cheers,
Good morning and happy new year!
I would like to let you know that I'm working on two new PEPs.
The first PEP addresses hash collision attacks as discussed in
http://bugs.python.org/issue14621. I'm planing to make the internal
string and bytes hash function more secure, pluggable and even faster.
