aboutsummaryrefslogtreecommitdiffstats
path: root/lib/ssl/doc/src/warning.gif
diff options
context:
space:
mode:
authorDániel Szoboszlay <[email protected]>2015-10-12 16:24:56 +0200
committerSverker Eriksson <[email protected]>2016-01-28 19:29:16 +0100
commit279cb5b1bba53b93384093530ae781fcf203756b (patch)
tree19e72f285f440876cf4451413008c2a7a2f6a1b9 /lib/ssl/doc/src/warning.gif
parent76d78818252f0223ee3cffe232a6333428d401a0 (diff)
downloadotp-279cb5b1bba53b93384093530ae781fcf203756b.tar.gz
otp-279cb5b1bba53b93384093530ae781fcf203756b.tar.bz2
otp-279cb5b1bba53b93384093530ae781fcf203756b.zip
Only use supported EC curves in crypto tests
Avoid hardcoding EC curve names in tests where it basically doesn't matter which curve is used. Take one of the supported curbes instead. Also, when testing ECDH key generation, skip unsupported curves. These changes are to simplify dealing with exotic libcrypto builds that don't support certain curves (for example RHEL disallows < 256 bit curves). The crypto application is only able to detect the supported curves on a very coarse level (ECC support in general and GF2m curves), so it may be necessary to edit the list of curves in the crypto_ec_curves modules. But that should be the only necessary modification to make the crypto tests pass.
Diffstat (limited to 'lib/ssl/doc/src/warning.gif')
0 files changed, 0 insertions, 0 deletions