1. 14 3月, 2020 1 次提交
    • B
      Code to thread-safety in ChangeCipherState · 44bad9cb
      Benjamin Kaduk 提交于
      The server-side ChangeCipherState processing stores the new cipher
      in the SSL_SESSION object, so that the new state can be used if
      this session gets resumed.  However, writing to the session is only
      thread-safe for initial handshakes, as at other times the session
      object may be in a shared cache and in use by another thread at the
      same time.  Reflect this invariant in the code by only writing to
      s->session->cipher when it is currently NULL (we do not cache sessions
      with no cipher).  The code prior to this change would never actually
      change the (non-NULL) cipher value in a session object, since our
      server enforces that (pre-TLS-1.3) resumptions use the exact same
      cipher as the initial connection, and non-abbreviated renegotiations
      have produced a new session object before we get to this point.
      Regardless, include logic to detect such a condition and abort the
      handshake if it occurs, to avoid any risk of inadvertently using
      the wrong cipher on a connection.
      Reviewed-by: NTomas Mraz <tmraz@fedoraproject.org>
      (Merged from https://github.com/openssl/openssl/pull/10943)
      
      (cherry picked from commit 2e3ec2e1578977fca830a47fd7f521e290540e6d)
      44bad9cb
  2. 27 2月, 2020 1 次提交
  3. 21 2月, 2020 1 次提交
  4. 15 2月, 2020 1 次提交
  5. 07 2月, 2020 1 次提交
  6. 06 2月, 2020 1 次提交
  7. 02 1月, 2020 1 次提交
  8. 16 12月, 2019 1 次提交
  9. 15 12月, 2019 1 次提交
  10. 17 11月, 2019 1 次提交
  11. 15 10月, 2019 2 次提交
  12. 03 10月, 2019 1 次提交
  13. 15 9月, 2019 1 次提交
  14. 10 9月, 2019 3 次提交
  15. 08 8月, 2019 1 次提交
  16. 06 8月, 2019 2 次提交
  17. 01 8月, 2019 1 次提交
  18. 31 7月, 2019 1 次提交
  19. 23 7月, 2019 1 次提交
  20. 24 7月, 2019 1 次提交
  21. 08 7月, 2019 1 次提交
  22. 02 7月, 2019 2 次提交
  23. 01 7月, 2019 2 次提交
  24. 24 6月, 2019 1 次提交
  25. 12 6月, 2019 2 次提交
  26. 06 6月, 2019 1 次提交
  27. 03 6月, 2019 1 次提交
    • S
      Add the content type attribute to additional CMS signerinfo. · d63d841f
      Shane Lontis 提交于
      Fixes #8923
      
      Found using the openssl cms -resign option.
      This uses an alternate path to do the signing which was not adding the required signed attribute
      content type. The content type attribute should always exist since it is required is there are
      any signed attributes.
      As the signing time attribute is always added in code, the content type attribute is also required.
      The CMS_si_check_attributes() method adds validity checks for signed and unsigned attributes
      e.g. The message digest attribute is a signed attribute that must exist if any signed attributes
      exist, it cannot be an unsigned attribute and there must only be one instance containing a single
      value.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/8944)
      
      (cherry picked from commit 19e512a8244a6f527d0194339a8f9fc45468537a)
      d63d841f
  28. 28 5月, 2019 3 次提交
  29. 24 5月, 2019 2 次提交
  30. 21 5月, 2019 1 次提交