QuasarApp/openssl
4
0
Fork 0
mirror of https://github.com/QuasarApp/openssl.git synced 2025-04-30 03:34:39 +00:00
Code Issues Projects Releases Wiki Activity

More early data documentation updates following feedback

Browse Source 
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2737)
This commit is contained in:
Matt Caswell 2017-03-02 17:40:43 +00:00
parent cd9f7f624e
commit 83750d9b2b
2 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/man1/s_server.pod
View File

@ -529,11 +529,12 @@ The list should contain most wanted protocols first.
Protocol names are printable ASCII strings, for example "http/1.1" or Protocol names are printable ASCII strings, for example "http/1.1" or
"spdy/3". "spdy/3".
=item B<-max_early_data> =item B<-max_early_data arg>
Change the default maximum early data bytes that are specified for new sessions Change the default maximum early data bytes that are specified for new sessions
and any incoming early data (when used in conjunction with the B<-early_data> and any incoming early data (when used in conjunction with the B<-early_data>
flag). The default value is approximately 16k. flag). The default value is approximately 16k. The argument must be an integer
greater than or equal to 0.
=item B<-early_data> =item B<-early_data>

2
doc/man3/SSL_read_early.pod → doc/man3/SSL_read_early_data.pod
View File

@ -42,7 +42,7 @@ Early data has weaker security properties than other data sent over an SSL/TLS
connection. In particular the data does not have forward secrecy and there are connection. In particular the data does not have forward secrecy and there are
no guarantees that the same early data was not replayed across multiple no guarantees that the same early data was not replayed across multiple
connections. For this reason extreme care should be exercised when using early connections. For this reason extreme care should be exercised when using early
data. data. For specific details, consult the TLS 1.3 specification.
When a server receives early data it may opt to immediately respond by sending When a server receives early data it may opt to immediately respond by sending
application data back to the client. Data sent by the server at this stage is application data back to the client. Data sent by the server at this stage is