An error occurred fetching the project authors.
  1. 08 Sep, 2014 1 commit
  2. 26 Sep, 2013 1 commit
  3. 17 Sep, 2013 1 commit
  4. 29 Aug, 2013 1 commit
  5. 17 Jul, 2013 1 commit
  6. 02 Jul, 2013 1 commit
  7. 19 Jun, 2013 1 commit
    • Adam Langley's avatar
      crypto/tls: change advertised ciphersuite order. · 966e8896
      Adam Langley authored
      TLS clients send ciphersuites in preference order (most prefereable
      first). This change alters the order so that ECDHE comes before plain
      RSA, and RC4 comes before AES (because of the Lucky13 attack).
      
      This is unlikely to have much effect: as a server, the code uses the
      client's ciphersuite order by default and, as a client, the non-Go
      server probably imposes its order.
      
      R=golang-dev, r, raggi, jsing
      CC=golang-dev
      https://golang.org/cl/10372045
      966e8896
  8. 05 Jun, 2013 1 commit
  9. 18 May, 2012 1 commit
  10. 12 Apr, 2012 1 commit
  11. 19 Jan, 2012 1 commit
  12. 06 Dec, 2011 1 commit
  13. 02 Dec, 2011 1 commit
  14. 01 Dec, 2011 1 commit
  15. 28 Nov, 2011 1 commit
  16. 02 Nov, 2011 1 commit
  17. 11 Oct, 2011 1 commit
  18. 14 Sep, 2011 1 commit
    • Adam Langley's avatar
      crypto/tls: support SSLv3 · a775fbf8
      Adam Langley authored
      It would be nice not to have to support this since all the clients
      that we care about support TLSv1 by now. However, due to buggy
      implementations of SSLv3 on the Internet which can't do version
      negotiation correctly, browsers will sometimes switch to SSLv3. Since
      there's no good way for a browser tell a network problem from a buggy
      server, this downgrade can occur even if the server in question is
      actually working correctly.
      
      So we need to support SSLv3 for robustness :(
      
      Fixes #1703.
      
      R=bradfitz
      CC=golang-dev
      https://golang.org/cl/5018045
      a775fbf8
  19. 16 Dec, 2010 1 commit
  20. 15 Dec, 2010 2 commits