diff options
| author | Veres Lajos <vlajos@gmail.com> | 2013-06-13 01:22:32 +0200 |
|---|---|---|
| committer | Ben Laurie <ben@links.org> | 2013-09-05 22:39:42 +0200 |
| commit | 478b50cf67d6a91fdcd584cff57c58b7e863055d (patch) | |
| tree | 2503e85a768e8bde5edace29c80222b47ea1f0ea /bugs | |
| parent | Clean up layout. (diff) | |
| download | openssl-478b50cf67d6a91fdcd584cff57c58b7e863055d.tar.xz openssl-478b50cf67d6a91fdcd584cff57c58b7e863055d.zip | |
misspellings fixes by https://github.com/vlajos/misspell_fixer
Diffstat (limited to 'bugs')
| -rw-r--r-- | bugs/sslref.dif | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bugs/sslref.dif b/bugs/sslref.dif index 0aa92bfe6d..0817009bb4 100644 --- a/bugs/sslref.dif +++ b/bugs/sslref.dif @@ -17,10 +17,10 @@ is returned as 1. ===== I have not tested the following but it is reported by holtzman@mit.edu. -SSLref clients wait to recieve a server-verify before they send a +SSLref clients wait to receive a server-verify before they send a client-finished. Besides this not being evident from the examples in 2.2.1, it makes more sense to always send all packets you can before -reading. SSLeay was waiting in the server to recieve a client-finish +reading. SSLeay was waiting in the server to receive a client-finish before sending the server-verify :-). I have changed SSLeay to send a server-verify before trying to read the client-finished. |