diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ssl/SSL_CIPHER_get_name.pod | 2 | ||||
| -rw-r--r-- | doc/ssl/SSL_CTX_set_verify.pod | 2 | ||||
| -rw-r--r-- | doc/ssl/SSL_SESSION_free.pod | 2 | ||||
| -rw-r--r-- | doc/ssl/SSL_free.pod | 2 | ||||
| -rw-r--r-- | doc/ssleay.txt | 4 |
5 files changed, 6 insertions, 6 deletions
diff --git a/doc/ssl/SSL_CIPHER_get_name.pod b/doc/ssl/SSL_CIPHER_get_name.pod index f81f692df5..f62a869a9b 100644 --- a/doc/ssl/SSL_CIPHER_get_name.pod +++ b/doc/ssl/SSL_CIPHER_get_name.pod @@ -28,7 +28,7 @@ SSL_CIPHER_get_version() returns the protocol version for B<cipher>, currently SSL_CIPHER_description() returns a textual description of the cipher used into the buffer B<buf> of length B<len> provided. B<len> must be at least -128 bytes, otherwise a pointer to the the string "Buffer too small" is +128 bytes, otherwise a pointer to the string "Buffer too small" is returned. If B<buf> is NULL, a buffer of 128 bytes is allocated using OPENSSL_malloc(). If the allocation fails, a pointer to the string "OPENSSL_malloc Error" is returned. diff --git a/doc/ssl/SSL_CTX_set_verify.pod b/doc/ssl/SSL_CTX_set_verify.pod index ca8d81b82c..81566839d3 100644 --- a/doc/ssl/SSL_CTX_set_verify.pod +++ b/doc/ssl/SSL_CTX_set_verify.pod @@ -28,7 +28,7 @@ specifies the B<verify_callback> function to be used. If no callback function shall be specified, the NULL pointer can be used for B<verify_callback>. In this case last B<verify_callback> set specifically for this B<ssl> remains. If no special B<callback> was set before, the default callback for the underlying -B<ctx> is used, that was valid at the the time B<ssl> was created with +B<ctx> is used, that was valid at the time B<ssl> was created with L<SSL_new(3)|SSL_new(3)>. SSL_CTX_set_verify_depth() sets the maximum B<depth> for the certificate chain diff --git a/doc/ssl/SSL_SESSION_free.pod b/doc/ssl/SSL_SESSION_free.pod index 558de01df9..110ec73ab6 100644 --- a/doc/ssl/SSL_SESSION_free.pod +++ b/doc/ssl/SSL_SESSION_free.pod @@ -14,7 +14,7 @@ SSL_SESSION_free - free an allocated SSL_SESSION structure SSL_SESSION_free() decrements the reference count of B<session> and removes the B<SSL_SESSION> structure pointed to by B<session> and frees up the allocated -memory, if the the reference count has reached 0. +memory, if the reference count has reached 0. =head1 NOTES diff --git a/doc/ssl/SSL_free.pod b/doc/ssl/SSL_free.pod index 2d4f8b6168..13c1abd9ec 100644 --- a/doc/ssl/SSL_free.pod +++ b/doc/ssl/SSL_free.pod @@ -14,7 +14,7 @@ SSL_free - free an allocated SSL structure SSL_free() decrements the reference count of B<ssl>, and removes the SSL structure pointed to by B<ssl> and frees up the allocated memory if the -the reference count has reached 0. +reference count has reached 0. =head1 NOTES diff --git a/doc/ssleay.txt b/doc/ssleay.txt index c75312911f..a8b04d7059 100644 --- a/doc/ssleay.txt +++ b/doc/ssleay.txt @@ -3800,9 +3800,9 @@ made public on sci.crypt in Sep 1994 (RC4) and Feb 1996 (RC2). I have copies of the origional postings if people are interested. RSA I believe claim that they were 'trade-secrets' and that some-one broke an NDA in revealing them. Other claim they reverse engineered the algorithms from -compiled binaries. If the algorithms were reverse engineered, I belive +compiled binaries. If the algorithms were reverse engineered, I believe RSA had no legal leg to stand on. If an NDA was broken, I don't know. -Regardless, RSA, I belive, is willing to go to court over the issue so +Regardless, RSA, I believe, is willing to go to court over the issue so licencing is probably the best idea, or at least talk to them. If there are people who actually know more about this, pease let me know, I don't want to vilify or spread miss-information if I can help it. |