# Timeline for What's the structure of server-key-exchange message during TLS handshake

### Current License: CC BY-SA 3.0

10 events
when toggle format what by license comment
Oct 7 '21 at 7:34 history edited CommunityBot
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
Oct 9 '15 at 4:22 comment @Z.T. You're right, the version is TLS 1.0 when I see the missing algorithm field. Thanks for the pointer to the RFC and openssl code.
Oct 7 '15 at 20:53 comment @juhraffe I think you see TLS version before 1.2. See RFC 5246 Section 7.4.3 "Note that the introduction of the algorithm field is a change from previous versions". Also see openssl code, e.g.: github.com/openssl/openssl/blob/master/ssl/t1_trce.c#L664 SSL_USE_SIGALGS is true only if TLS1.2 was negotiated.
Oct 6 '15 at 2:54 comment I'm seeing a similar server key exchange message, but without the "06 01" (signature algorithm). Everything else is byte-for-byte identical to the message listed, except of course the ECDHE key values. This seems to happen when I disable the "signature hash algorithm" (0x000d) client hello extension.
Jun 18 '15 at 11:54 comment And to complete one detail, opaque signature<0..2^16-1> means signature is a TLS "vector" that starts with a 2-octet bigendian length prefix. The "01 00" called out in the question is the length prefix 256 for the RSA signature value, which is just a bigendian integer.
Jun 17 '15 at 18:11 history edited
deleted 127 characters in body
Jun 17 '15 at 18:01 history edited