summaryrefslogtreecommitdiffstats
path: root/lib/libssl/src/test
diff options
context:
space:
mode:
authormiod <miod@openbsd.org>2014-04-17 18:16:45 +0000
committermiod <miod@openbsd.org>2014-04-17 18:16:45 +0000
commit71a94becd57c2fb84d531dc50aa1f1a4031889cf (patch)
treeb46b9baaec5e4d4adfc0966aadc109f273be7a42 /lib/libssl/src/test
parentspidey senses (diff)
downloadwireguard-openbsd-71a94becd57c2fb84d531dc50aa1f1a4031889cf.tar.xz
wireguard-openbsd-71a94becd57c2fb84d531dc50aa1f1a4031889cf.zip
Ok, there was a need for OPENSSL_cleanse() instead of bzero() to prevent
supposedly smart compilers from optimizing memory cleanups away. Understood. Ok, in case of an hypothetically super smart compiler, OPENSSL_cleanse() had to be convoluted enough for the compiler not to recognize that this was actually bzero() in disguise. Understood. But then why there had been optimized assembler versions of OPENSSL_cleanse() is beyond me. Did someone not trust the C obfuscation?
Diffstat (limited to 'lib/libssl/src/test')
0 files changed, 0 insertions, 0 deletions