summaryrefslogtreecommitdiffstats
path: root/Modules/_blake2/blake2b_impl.c
Commit message (Collapse)AuthorAgeFilesLines
* [3.6] bpo-33729: Fix issues with arguments parsing in hashlib. (GH-8346) ↵Serhiy Storchaka2018-10-111-32/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | (GH-8581) (GH-9657) * help(hashlib) didn't work because of incorrect module name in blake2b and blake2s classes. * Constructors blake2*(), sha3_*(), shake_*() and keccak_*() incorrectly accepted keyword argument "string" for binary data, but documented as accepting the "data" keyword argument. Now this parameter is positional-only. * Keyword-only parameters in blake2b() and blake2s() were not documented as keyword-only. * Default value for some parameters of blake2b() and blake2s() was None, which is not acceptable value. * The length argument for shake_*.digest() was wrapped out to 32 bits. * The argument for shake_128.digest() and shake_128.hexdigest() was not positional-only as intended. * TypeError messages for incorrect arguments in all constructors sha3_*(), shake_*() and keccak_*() incorrectly referred to sha3_224. Also made the following enhancements: * More accurately specified input and result types for strings, bytes and bytes-like objects. * Unified positional parameter names for update() and constructors. * Improved formatting. (cherry picked from commit f1d36d8efaecd5c84cb35e35119b283f37d83c40) (cherry picked from commit 47957dab94a4efa2fee61c9a8193f78300950769)
* [3.6] Fix misleading mentions of tp_size in comments (GH-9137)Benjamin Peterson2018-09-101-1/+1
| | | | | | | Many type object initializations labeled a field "tp_size" in the comment, but the name of that field is tp_basicsize.. (cherry picked from commit 0e0bc4e221f592f305d335faf5f8046484eb9238) Co-authored-by: Peter Eisentraut <peter@eisentraut.org>
* bpo-31933: fix blake2 multi-byte params on big endian platforms (GH-4250) ↵Miss Islington (bot)2017-11-031-2/+4
| | | | | | | | | | | | | | | (#4262) All Blake2 params have to be encoded in little-endian byte order. For the two multi-byte integer params, leaf_length and node_offset, that means that assigning a native-endian integer to them appears to work on little-endian platforms, but gives the wrong result on big-endian. The current libb2 API doesn't make that very clear, and @sneves is working on new API functions in the GH issue above. In the meantime, we can work around the problem by explicitly assigning little-endian values to the parameter block. See https://github.com/BLAKE2/libb2/issues/12. (cherry picked from commit dcfb0e3c04f1b29a0d09bb0a81dcd5ee5a5fef1a)
* more PY_LONG_LONG to long longBenjamin Peterson2016-09-081-2/+2
|
* Silence two warnings in blake2. key_length is between 0 and 64 (block size).Christian Heimes2016-09-071-1/+1
|
* Issue #26798: Add BLAKE2 (blake2b and blake2s) to hashlib.Christian Heimes2016-09-061-0/+460