summaryrefslogtreecommitdiff
path: root/src/lib/libssl/d1_lib.c
diff options
context:
space:
mode:
authormiod <>2015-03-18 05:26:10 +0000
committermiod <>2015-03-18 05:26:10 +0000
commit6b3d8d3164d1b68d078a0cf83583f3dd8bbcb340 (patch)
treee1d52e8097383e7013cf5ce2bd929fe8f0cfaa67 /src/lib/libssl/d1_lib.c
parent4fb860a66d9312261140bce7cdc5fbdef4e6e43a (diff)
downloadopenbsd-6b3d8d3164d1b68d078a0cf83583f3dd8bbcb340.tar.gz
openbsd-6b3d8d3164d1b68d078a0cf83583f3dd8bbcb340.tar.bz2
openbsd-6b3d8d3164d1b68d078a0cf83583f3dd8bbcb340.zip
In the neverending saga of enabling and disabling assembler code for sha
routines on hppa, the cause for sha512-parisc subtly misbehaving has been found: despite having fallback pa1.1 code when running on a 32-bit cpu, the shift constants used in the sigma computations in sha512 are >= 32 and are silently truncated to 5 bits by the assembler, so there is no chance of getting this code to work on a non-pa2.0 processor. However, the pa1.1 fallback code for sha256 is safe, as it never attempts to shift by more than 31, so reenable it again.
Diffstat (limited to 'src/lib/libssl/d1_lib.c')
0 files changed, 0 insertions, 0 deletions