ChangeLog 1.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. 2007-05-22 Sebastien Pouliot <[email protected]>
  2. * TlsClientCertificate.cs: Add chain support for x.509 client
  3. certificates. Based on Roy Versteeg patch to fix #80557.
  4. 2007-05-07 Sebastien Pouliot <[email protected]>
  5. * TlsClientCertificate.cs: A client certficate with a RSA public key
  6. can only be used, protocol wise, to sign. Which means we should always
  7. be checking it's keyUsage for digitalSignature. Fix for bug #81511
  8. 2006-09-11 Sebastien Pouliot <[email protected]>
  9. * TlsClientCertificate.cs: Use Negotiating.Cipher instead of Cipher.
  10. Fix reading the message length if it's zero (in that case it's not
  11. present two times).
  12. * TlsClientFinished.cs: Use Current.Cipher instead of Cipher. Use
  13. Compare to test client and server digests equality.
  14. * TlsClientHello.cs: Use Negotiating.Cipher instead of Cipher.
  15. * TlsClientKeyExchange.cs: Use Negotiating.Cipher instead of Cipher.
  16. * TlsServerFinished.cs: Use Current.Cipher instead of Cipher.
  17. * TlsServerHello.cs: Use Negotiating.Cipher instead of Cipher.
  18. 2005-07-01 Sebastien Pouliot <[email protected]>
  19. * TlsClientCertificate.cs: Fix decoding (extra length) and for null
  20. (no certificates). Add basic client certificate validations before
  21. calling the callback (which can override the default decision).
  22. * TlsClientCertificateVerify.cs: Fix signature verification (the first
  23. two bytes are the length of the signature).
  24. * TlsServerCertificateRequest.cs: Sent the list of trusted root DNs.
  25. 2004-11-10 Sebastien Pouliot <[email protected]>
  26. * TlsClientFinished.cs: ProcessAsTls1 - get out of the loop if PRF are
  27. different.
  28. 2004-09-23 Sebastien Pouliot <[email protected]>
  29. * TlsClientKeyExchange.cs: Removed .Clear call on private key as itn't
  30. ours (but only a reference). It also requires the callback to recreate
  31. a new key object each time (which is worse). This also implies that
  32. the caller (implementing the callback) is responsible to clear it.