sslref.dif 1.1 KB

1234567891011121314151617181920212223242526
  1. The February 9th, 1995 version of the SSL document differs from
  2. https://www.netscape.com in the following ways.
  3. =====
  4. The key material for generating a SSL_CK_DES_64_CBC_WITH_MD5 key is
  5. KEY-MATERIAL-0 = MD5[MASTER-KEY,"0",CHALLENGE,CONNECTION-ID]
  6. not
  7. KEY-MATERIAL-0 = MD5[MASTER-KEY,CHALLENGE,CONNECTION-ID]
  8. as specified in the documentation.
  9. =====
  10. From the section 2.6 Server Only Protocol Messages
  11. If the SESSION-ID-HIT flag is non-zero then the CERTIFICATE-TYPE,
  12. CERTIFICATE-LENGTH and CIPHER-SPECS-LENGTH fields will be zero.
  13. This is not true for https://www.netscape.com. The CERTIFICATE-TYPE
  14. is returned as 1.
  15. =====
  16. I have not tested the following but it is reported by holtzman@mit.edu.
  17. SSLref clients wait to recieve a server-verify before they send a
  18. client-finished. Besides this not being evident from the examples in
  19. 2.2.1, it makes more sense to always send all packets you can before
  20. reading. SSLeay was waiting in the server to recieve a client-finish
  21. before sending the server-verify :-). I have changed SSLeay to send a
  22. server-verify before trying to read the client-finished.