summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2015-05-26 09:55:06 -0400
committerMatt Caswell <matt@openssl.org>2015-05-28 16:05:49 +0100
commit7470cefcb249ea37f97c65e64628c1994725462d (patch)
tree4d4513b181cbe83b2057771c20030737225387ef
parent858618e7e037559b75b0bfca4d30440f9515b888 (diff)
Clarify that SSL3_RANDOM_SIZE is a constant, for now.
Signed-off-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org>
-rw-r--r--doc/ssl/SSL_get_client_random.pod18
1 files changed, 12 insertions, 6 deletions
diff --git a/doc/ssl/SSL_get_client_random.pod b/doc/ssl/SSL_get_client_random.pod
index e31d3f0a28..bec45d7e0e 100644
--- a/doc/ssl/SSL_get_client_random.pod
+++ b/doc/ssl/SSL_get_client_random.pod
@@ -15,12 +15,12 @@ SSL_get_client_random, SSL_get_server_random, SSL_SESSION_get_master_key - retri
=head1 DESCRIPTION
SSL_get_client_random() extracts the random value sent from the client
-to the server during the initial SSL/TLS handshake. It copies this
-value into the buffer provided in B<out>, which must have at least
-B<outlen> bytes available. It returns the total number of bytes that were
-actually copied.
-If B<outlen> is less than zero, SSL_get_client_random() copies nothing, and
-returns the total size of the client_random value.
+to the server during the initial SSL/TLS handshake. It copies as many
+bytes as it can of this value into the buffer provided in B<out>,
+which must have at least B<outlen> bytes available. It returns the
+total number of bytes that were actually copied. If B<outlen> is less
+than zero, SSL_get_client_random() copies nothing, and returns the
+total size of the client_random value.
SSL_get_server_random() behaves the same, but extracts the random value
sent from the server to the client during the initial SSL/TLS handshake.
@@ -50,6 +50,12 @@ If you need to calculate another secret value that depends on the master
secret, you should probably use SSL_export_keying_material() instead, and
forget that you ever saw these functions.
+In current versions of the TLS protocols, the length of client_random
+(and also server_random) is always SSL3_RANDOM_SIZE bytes. Support for
+other outlen arguments to the SSL_get_*_random() functions is provided
+in case of the unlikely event that a future version or variant of TLS
+uses some other length there.
+
Finally, though the "client_random" and "server_random" values are called
"random", many TLS implementations will generate four bytes of those
values based on their view of the current time.