1. 25 1月, 2018 2 次提交
  2. 19 1月, 2018 1 次提交
  3. 02 1月, 2018 1 次提交
  4. 29 12月, 2017 1 次提交
  5. 14 12月, 2017 6 次提交
  6. 09 12月, 2017 1 次提交
  7. 04 12月, 2017 3 次提交
  8. 12 11月, 2017 1 次提交
  9. 06 11月, 2017 1 次提交
  10. 11 10月, 2017 1 次提交
  11. 07 10月, 2017 1 次提交
  12. 06 10月, 2017 1 次提交
  13. 04 10月, 2017 1 次提交
    • T
      Session resume broken switching contexts · a84e5c9a
      Todd Short 提交于
      When an SSL's context is swtiched from a ticket-enabled context to
      a ticket-disabled context in the servername callback, no session-id
      is generated, so the session can't be resumed.
      
      If a servername callback changes the SSL_OP_NO_TICKET option, check
      to see if it's changed to disable, and whether a session ticket is
      expected (i.e. the client indicated ticket support and the SSL had
      tickets enabled at the time), and whether we already have a previous
      session (i.e. s->hit is set).
      
      In this case, clear the ticket-expected flag, remove any ticket data
      and generate a session-id in the session.
      
      If the SSL hit (resumed) and switched to a ticket-disabled context,
      assume that the resumption was via session-id, and don't bother to
      update the session.
      
      Before this fix, the updated unit-tests in 06-sni-ticket.conf would
      fail test #4 (server1 = SNI, server2 = no SNI).
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      Reviewed-by: NPaul Dale <paul.dale@oracle.com>
      (Merged from https://github.com/openssl/openssl/pull/1529)
      a84e5c9a
  14. 28 9月, 2017 1 次提交
  15. 26 9月, 2017 6 次提交
  16. 23 9月, 2017 1 次提交
  17. 20 9月, 2017 1 次提交
  18. 09 9月, 2017 1 次提交
  19. 06 9月, 2017 1 次提交
  20. 01 9月, 2017 1 次提交
  21. 31 8月, 2017 1 次提交
  22. 30 8月, 2017 3 次提交
  23. 18 8月, 2017 1 次提交
  24. 11 8月, 2017 1 次提交
  25. 03 8月, 2017 1 次提交