1. 11 5月, 2018 5 次提交
  2. 08 5月, 2018 3 次提交
  3. 03 5月, 2018 2 次提交
  4. 02 5月, 2018 1 次提交
    • B
      Fix regression with session cache use by clients · c4fa1f7f
      Benjamin Kaduk 提交于
      Commit d316cdcf introduced some extra
      checks into the session-cache update procedure, intended to prevent
      the caching of sessions whose resumption would lead to a handshake
      failure, since if the server is authenticating the client, there needs to
      be an application-set "session id context" to match up to the authentication
      context.  While that change is effective for its stated purpose, there
      was also some collatoral damage introduced along with the fix -- clients
      that set SSL_VERIFY_PEER are not expected to set an sid_ctx, and so
      their usage of session caching was erroneously denied.
      
      Fix the scope of the original commit by limiting it to only acting
      when the SSL is a server SSL.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5967)
      c4fa1f7f
  5. 01 5月, 2018 1 次提交
  6. 27 4月, 2018 2 次提交
  7. 26 4月, 2018 1 次提交
  8. 25 4月, 2018 1 次提交
  9. 24 4月, 2018 4 次提交
  10. 20 4月, 2018 2 次提交
  11. 18 4月, 2018 4 次提交
  12. 17 4月, 2018 5 次提交
  13. 05 4月, 2018 1 次提交
    • M
      Move the loading of the ssl_conf module to libcrypto · d8f031e8
      Matt Caswell 提交于
      The GOST engine needs to be loaded before we initialise libssl. Otherwise
      the GOST ciphersuites are not enabled. However the SSL conf module must
      be loaded before we initialise libcrypto. Otherwise we will fail to read
      the SSL config from a config file properly.
      
      Another problem is that an application may make use of both libcrypto and
      libssl. If it performs libcrypto stuff first and OPENSSL_init_crypto()
      is called and loads a config file it will fail if that config file has
      any libssl stuff in it.
      
      This commit separates out the loading of the SSL conf module from the
      interpretation of its contents. The loading piece doesn't know anything
      about SSL so this can be moved to libcrypto. The interpretation of what it
      means remains in libssl. This means we can load the SSL conf data before
      libssl is there and interpret it when it later becomes available.
      
      Fixes #5809
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5818)
      d8f031e8
  14. 04 4月, 2018 2 次提交
  15. 03 4月, 2018 2 次提交
  16. 31 3月, 2018 3 次提交
  17. 29 3月, 2018 1 次提交