Jean-Philippe Aumasson

That could be an optimization indeed, I may implement it later, or happy to take a PR :)

Yeah this is missing, sorry. I'll probably add, but at the moment that's not on the top of my todo list.

Yeah you can do this, but a codebook attack in 2^32 is even more efficient :)

Shannon knew nothing about cryptography!

let's stick to `switch`, thanks @jedisct1 @demerphq for your input.

Still does not support arbitrary data (ie that includes null bytes); why be limited to strings?

Thanks, but I still don't understand why strings with null bytes are not supported; why should the API be limited to strings of characters, rather than arbitrary byte strings? On...

Have not tried the module, just read "Pull Request #3: string containing \x00 raises unexpected exception." on https://github.com/darjeeling/python-blake2/issues/2 On Tue, Feb 19, 2013 at 8:03 AM, EUNJO WI [email protected] wrote:...

Ok, sorry for misunderstanding. There is something strange though: > > > > import blake2 > > > > blake2.blake2('\x00') > > > > '507ed301000000008fa05700000000004098d3010000000025c15700000000000005da01000000001c104135167f000078cabc00ff7f000080cabc00ff7f0000' > > > > blake2.blake2('\x00')...

Sorry for the delay. Our FROST version uses BLAKE3, where IETF mandates SHA-2 or SHAKE, which is already a deviation from the standard.