aboutsummaryrefslogtreecommitdiffstats
path: root/doc/ssl/SSL_CTX_set_options.pod
diff options
context:
space:
mode:
authorUlf Möller <ulf@openssl.org>2001-02-16 02:09:53 +0000
committerUlf Möller <ulf@openssl.org>2001-02-16 02:09:53 +0000
commit52d160d85d2a4c57729540d409747071f6b952f7 (patch)
tree997458cfe9676869823a9613ca96f079ea5b83bc /doc/ssl/SSL_CTX_set_options.pod
parent54ff1e6ae5b8c566d7c9f83b236e944ea0bf5135 (diff)
downloadopenssl-52d160d85d2a4c57729540d409747071f6b952f7.tar.gz
ispell
Diffstat (limited to 'doc/ssl/SSL_CTX_set_options.pod')
-rw-r--r--doc/ssl/SSL_CTX_set_options.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ssl/SSL_CTX_set_options.pod b/doc/ssl/SSL_CTX_set_options.pod
index fe164feaab..5eb376eda8 100644
--- a/doc/ssl/SSL_CTX_set_options.pod
+++ b/doc/ssl/SSL_CTX_set_options.pod
@@ -53,7 +53,7 @@ Netscape-Commerce/1.12, when talking SSLv2, accepts a 32 byte
challenge but then appears to only use 16 bytes when generating the
encryption keys. Using 16 bytes is ok but it should be ok to use 32.
According to the SSLv3 spec, one should use 32 bytes for the challenge
-when opperating in SSLv2/v3 compatablity mode, but as mentioned above,
+when operating in SSLv2/v3 compatibility mode, but as mentioned above,
this breaks this server so 16 bytes is the way to go.
=item SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG
@@ -133,7 +133,7 @@ Also use the temporary RSA key when doing RSA operations.
When choosing a cipher, use the server's preferences instead of the client
preferences. When not set, the SSL server will always follow the clients
preferences. When set, the SSLv3/TLSv1 server will choose following its
-own preferences. Because of the different procotol, for SSLv2 the server
+own preferences. Because of the different protocol, for SSLv2 the server
will send his list of preferences to the client and the client chooses.
=item SSL_OP_PKCS1_CHECK_1