summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/buffer/buffer.h
diff options
context:
space:
mode:
authorjsing <>2014-10-15 17:39:34 +0000
committerjsing <>2014-10-15 17:39:34 +0000
commit2eef89d9c3ef3349d47fd880aae495afdc0b61ef (patch)
tree7b13b9e7e81fc1ddf031b897badcd5def78ba440 /src/lib/libcrypto/buffer/buffer.h
parentfb2295a243990c62c45ad1bf4dd5b796d118ae38 (diff)
downloadopenbsd-2eef89d9c3ef3349d47fd880aae495afdc0b61ef.tar.gz
openbsd-2eef89d9c3ef3349d47fd880aae495afdc0b61ef.tar.bz2
openbsd-2eef89d9c3ef3349d47fd880aae495afdc0b61ef.zip
Disable SSLv3 by default.
SSLv3 has been long known to have weaknesses and the POODLE attack has once again shown that it is effectively broken/insecure. As such, it is time to stop enabling a protocol was deprecated almost 15 years ago. If an application really wants to provide backwards compatibility, at the cost of security, for now SSL_CTX_clear_option(ctx, SSL_OP_NO_SSLv3) can be used to re-enable it on a per-application basis. General agreement from many. ok miod@
Diffstat (limited to 'src/lib/libcrypto/buffer/buffer.h')
0 files changed, 0 insertions, 0 deletions