summaryrefslogtreecommitdiffstats
path: root/Doc/reference
diff options
context:
space:
mode:
authorJack O'Connor <oconnor663@gmail.com>2017-11-03 19:02:41 (GMT)
committerChristian Heimes <christian@python.org>2017-11-03 19:02:41 (GMT)
commitdcfb0e3c04f1b29a0d09bb0a81dcd5ee5a5fef1a (patch)
tree4f160c37de78a47989bdabea0bdb3f3a44330c99 /Doc/reference
parentf6f90ff079a22b79a58d47b6117cc8a8c7d366f3 (diff)
downloadcpython-dcfb0e3c04f1b29a0d09bb0a81dcd5ee5a5fef1a.zip
cpython-dcfb0e3c04f1b29a0d09bb0a81dcd5ee5a5fef1a.tar.gz
cpython-dcfb0e3c04f1b29a0d09bb0a81dcd5ee5a5fef1a.tar.bz2
bpo-31933: fix blake2 multi-byte params on big endian platforms (#4250)
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.
Diffstat (limited to 'Doc/reference')
0 files changed, 0 insertions, 0 deletions