1. 26 1月, 2018 1 次提交
    • B
      Add TLS 1.3 draft-23 PSS signature algorithms · f55e99f7
      Benjamin Kaduk 提交于
      We now have a split in the signature algorithms codepoint space for
      whether the certificate's key is for rsaEncryption or a PSS-specific
      key, which should let us get rid of some special-casing that we
      previously needed to try to coax rsaEncryption keys into performing PSS.
      (This will be done in a subsequent commit.)
      
      Send the new PSS-with-PSS-specific key first in our list, so that
      we prefer the new technology to the old one.
      
      We need to update the expected certificate type in one test,
      since the "RSA-PSS+SHA256" form now corresponds to a public key
      of type rsaEncryption, so we should expect the server certificate
      type to be just "RSA".  If we want to get a server certificate
      type of "RSA-PSS", we need to use a new signature algorithm
      that cannot be represented as signature+hash, so add a test for that
      as well.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5068)
      f55e99f7
  2. 25 1月, 2018 2 次提交
  3. 19 1月, 2018 1 次提交
  4. 02 1月, 2018 1 次提交
  5. 29 12月, 2017 1 次提交
  6. 14 12月, 2017 6 次提交
  7. 09 12月, 2017 1 次提交
  8. 04 12月, 2017 3 次提交
  9. 12 11月, 2017 1 次提交
  10. 06 11月, 2017 1 次提交
  11. 11 10月, 2017 1 次提交
  12. 07 10月, 2017 1 次提交
  13. 06 10月, 2017 1 次提交
  14. 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
  15. 28 9月, 2017 1 次提交
  16. 26 9月, 2017 6 次提交
  17. 23 9月, 2017 1 次提交
  18. 20 9月, 2017 1 次提交
  19. 09 9月, 2017 1 次提交
  20. 06 9月, 2017 1 次提交
  21. 01 9月, 2017 1 次提交
  22. 31 8月, 2017 1 次提交
  23. 30 8月, 2017 3 次提交
  24. 18 8月, 2017 1 次提交
  25. 11 8月, 2017 1 次提交