SSLv3 2.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. So far...
  2. ssl3.netscape.com:443 does not support client side dynamic
  3. session-renegotiation.
  4. ssl3.netscape.com:444 (asks for client cert) sends out all the CA RDN
  5. in an invalid format (the outer sequence is removed).
  6. Netscape-Commerce/1.12, when talking SSLv2, accepts a 32 byte
  7. challenge but then appears to only use 16 bytes when generating the
  8. encryption keys. Using 16 bytes is ok but it should be ok to use 32.
  9. According to the SSLv3 spec, one should use 32 bytes for the challenge
  10. when opperating in SSLv2/v3 compatablity mode, but as mentioned above,
  11. this breaks this server so 16 bytes is the way to go.
  12. www.microsoft.com - when talking SSLv2, if session-id reuse is
  13. performed, the session-id passed back in the server-finished message
  14. is different from the one decided upon.
  15. ssl3.netscape.com:443, first a connection is established with RC4-MD5.
  16. If it is then resumed, we end up using DES-CBC3-SHA. It should be
  17. RC4-MD5 according to 7.6.1.3, 'cipher_suite'.
  18. Netscape-Enterprise/2.01 (https://merchant.netscape.com) has this bug.
  19. It only really shows up when connecting via SSLv2/v3 then reconnecting
  20. via SSLv3. The cipher list changes....
  21. NEW INFORMATION. Try connecting with a cipher list of just
  22. DES-CBC-SHA:RC4-MD5. For some weird reason, each new connection uses
  23. RC4-MD5, but a re-connect tries to use DES-CBC-SHA. So netscape, when
  24. doing a re-connect, always takes the first cipher in the cipher list.
  25. If we accept a netscape connection, demand a client cert, have a
  26. non-self-signed CA which does not have it's CA in netscape, and the
  27. browser has a cert, it will crash/hang. Works for 3.x and 4.xbeta
  28. Netscape browsers do not really notice the server sending a
  29. close notify message. I was sending one, and then some invalid data.
  30. netscape complained of an invalid mac. (a fork()ed child doing a
  31. SSL_shutdown() and still sharing the socket with its parent).
  32. Netscape, when using export ciphers, will accept a 1024 bit temporary
  33. RSA key. It is supposed to only accept 512.
  34. If Netscape connects to a server which requests a client certificate
  35. it will frequently hang after the user has selected one and never
  36. complete the connection. Hitting "Stop" and reload fixes this and
  37. all subsequent connections work fine. This appears to be because
  38. Netscape wont read any new records in when it is awaiting a server
  39. done message at this point. The fix is to send the certificate request
  40. and server done messages in one record.