diff options
author | FdaSilvaYY <fdasilvayy@gmail.com> | 2016-05-01 19:52:58 +0200 |
---|---|---|
committer | Rich Salz <rsalz@openssl.org> | 2016-05-01 19:14:57 -0400 |
commit | 24c2cd3967ed23acc0bd31a3781c4525e2e42a2c (patch) | |
tree | ca10d9e7154f2bd7cf32216c6be51ad526cc7a0e /doc/ssl | |
parent | e0f96357e4b77e452966312a0542ec9cb0eb87bd (diff) |
Fix spelling in pod files
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
Diffstat (limited to 'doc/ssl')
-rw-r--r-- | doc/ssl/SSL_COMP_add_compression_method.pod | 2 | ||||
-rw-r--r-- | doc/ssl/SSL_CONF_cmd.pod | 2 | ||||
-rw-r--r-- | doc/ssl/SSL_CTX_set_min_proto_version.pod | 2 | ||||
-rw-r--r-- | doc/ssl/SSL_CTX_set_split_send_fragment.pod | 2 | ||||
-rw-r--r-- | doc/ssl/SSL_CTX_use_certificate.pod | 2 | ||||
-rw-r--r-- | doc/ssl/SSL_get_client_random.pod | 2 | ||||
-rw-r--r-- | doc/ssl/SSL_get_shared_sigalgs.pod | 2 |
7 files changed, 7 insertions, 7 deletions
diff --git a/doc/ssl/SSL_COMP_add_compression_method.pod b/doc/ssl/SSL_COMP_add_compression_method.pod index fe10e1b45d..eb2689c4b9 100644 --- a/doc/ssl/SSL_COMP_add_compression_method.pod +++ b/doc/ssl/SSL_COMP_add_compression_method.pod @@ -26,7 +26,7 @@ It cannot be set for specific SSL_CTX or SSL objects. In versions of OpenSSL prior to 1.1.0 SSL_COMP_free_compression_methods() freed the internal table of compression methods that were built internally, and possibly augmented by adding SSL_COMP_add_compression_method(). However this is -now unncessary from version 1.1.0. No explicit initialisation or +now unnecessary from version 1.1.0. No explicit initialisation or de-initialisation is necessary. See L<OPENSSL_init_crypto(3)> and L<OPENSSL_init_ssl(3)>. From OpenSSL 1.1.0 calling this function does nothing. diff --git a/doc/ssl/SSL_CONF_cmd.pod b/doc/ssl/SSL_CONF_cmd.pod index 17b8758605..6748a05fb9 100644 --- a/doc/ssl/SSL_CONF_cmd.pod +++ b/doc/ssl/SSL_CONF_cmd.pod @@ -465,7 +465,7 @@ Set supported signature algorithms: SSL_CONF_cmd(ctx, "SignatureAlgorithms", "ECDSA+SHA256:RSA+SHA256:DSA+SHA256"); -There are various ways to select the supported procotols. +There are various ways to select the supported protocols. This set the minimum protocol version to TLSv1, and so disables SSLv3. This is the recommended way to disable protocols. diff --git a/doc/ssl/SSL_CTX_set_min_proto_version.pod b/doc/ssl/SSL_CTX_set_min_proto_version.pod index 535ae83e7a..8fcfba1d9f 100644 --- a/doc/ssl/SSL_CTX_set_min_proto_version.pod +++ b/doc/ssl/SSL_CTX_set_min_proto_version.pod @@ -17,7 +17,7 @@ and maximum supported protocol version =head1 DESCRIPTION -The functions set the minimum and maximum supported portocol versions +The functions set the minimum and maximum supported protocol versions for the B<ctx> or B<ssl>. This works in combination with the options set via L<SSL_CTX_set_options(3)> that also make it possible to disable diff --git a/doc/ssl/SSL_CTX_set_split_send_fragment.pod b/doc/ssl/SSL_CTX_set_split_send_fragment.pod index 9e7ab63b9a..ace1932383 100644 --- a/doc/ssl/SSL_CTX_set_split_send_fragment.pod +++ b/doc/ssl/SSL_CTX_set_split_send_fragment.pod @@ -58,7 +58,7 @@ explained further below. OpenSSL will only every use more than one pipeline if a ciphersuite is negotiated that uses a pipeline capable cipher provided by an engine. -Pipelining operates slighly differently for reading encrypted data compared to +Pipelining operates slightly differently for reading encrypted data compared to writing encrypted data. SSL_CTX_set_split_send_fragment() and SSL_set_split_send_fragment() define how data is split up into pipelines when writing encrypted data. The number of pipelines used will be determined by the diff --git a/doc/ssl/SSL_CTX_use_certificate.pod b/doc/ssl/SSL_CTX_use_certificate.pod index 13bb27702d..9838323825 100644 --- a/doc/ssl/SSL_CTX_use_certificate.pod +++ b/doc/ssl/SSL_CTX_use_certificate.pod @@ -72,7 +72,7 @@ B<file> into B<ctx>. The certificates must be in PEM format and must be sorted starting with the subject's certificate (actual client or server certificate), followed by intermediate CA certificates if applicable, and ending at the highest level (root) CA. SSL_use_certificate_chain_file() is -similar except it loads the cerificate chain into B<ssl>. +similar except it loads the certificate chain into B<ssl>. SSL_CTX_use_PrivateKey() adds B<pkey> as private key to B<ctx>. SSL_CTX_use_RSAPrivateKey() adds the private key B<rsa> of type RSA diff --git a/doc/ssl/SSL_get_client_random.pod b/doc/ssl/SSL_get_client_random.pod index 3db5a26b11..1bc7bceba0 100644 --- a/doc/ssl/SSL_get_client_random.pod +++ b/doc/ssl/SSL_get_client_random.pod @@ -41,7 +41,7 @@ details. Despite the names of SSL_get_client_random() and SSL_get_server_random(), they ARE NOT random number generators. Instead, they return the mostly-random values that -were already generated and used in the TLS protoccol. Using them +were already generated and used in the TLS protocol. Using them in place of RAND_bytes() would be grossly foolish. The security of your TLS session depends on keeping the master key secret: diff --git a/doc/ssl/SSL_get_shared_sigalgs.pod b/doc/ssl/SSL_get_shared_sigalgs.pod index ad305e6b5c..ce32aff5d9 100644 --- a/doc/ssl/SSL_get_shared_sigalgs.pod +++ b/doc/ssl/SSL_get_shared_sigalgs.pod @@ -65,7 +65,7 @@ The NIDs are OpenSSL equivalents. For example if the peer sent sha256(4) and rsa(1) then B<*rhash> would be 4, B<*rsign> 1, B<*phash> NID_sha256, B<*psig> NID_rsaEncryption and B<*psighash> NID_sha256WithRSAEncryption. -If a signature algorithm is not recognised the corresponsing NIDs +If a signature algorithm is not recognised the corresponding NIDs will be set to B<NID_undef>. This may be because the value is not supported or is not an appropriate combination (for example MD5 and DSA). |