1. 26 May, 2018 1 commit
  2. 24 May, 2018 2 commits
  3. 23 May, 2018 2 commits
    • Viktor Dukhovni's avatar
      Skip CN DNS name constraint checks when not needed · 6d3cfd13
      Viktor Dukhovni authored
      
      
      Only check the CN against DNS name contraints if the
      `X509_CHECK_FLAG_NEVER_CHECK_SUBJECT` flag is not set, and either the
      certificate has no DNS subject alternative names or the
      `X509_CHECK_FLAG_ALWAYS_CHECK_SUBJECT` flag is set.
      
      Add pertinent documentation, and touch up some stale text about
      name checks and DANE.
      
      Reviewed-by: default avatarMatt Caswell <matt@openssl.org>
      Reviewed-by: default avatarTim Hudson <tjh@openssl.org>
      6d3cfd13
    • Viktor Dukhovni's avatar
      Limit scope of CN name constraints · c2c2c7b3
      Viktor Dukhovni authored
      
      
      Don't apply DNS name constraints to the subject CN when there's a
      least one DNS-ID subjectAlternativeName.
      
      Don't apply DNS name constraints to subject CN's that are sufficiently
      unlike DNS names.  Checked name must have at least two labels, with
      all labels non-empty, no trailing '.' and all hyphens must be
      internal in each label.  In addition to the usual LDH characters,
      we also allow "_", since some sites use these for hostnames despite
      all the standards.
      
      Reviewed-by: default avatarMatt Caswell <matt@openssl.org>
      Reviewed-by: default avatarTim Hudson <tjh@openssl.org>
      c2c2c7b3
  4. 21 May, 2018 2 commits
  5. 20 May, 2018 3 commits
  6. 19 May, 2018 1 commit
  7. 18 May, 2018 1 commit
  8. 17 May, 2018 2 commits
  9. 16 May, 2018 1 commit
  10. 15 May, 2018 1 commit
  11. 14 May, 2018 2 commits
  12. 12 May, 2018 3 commits
  13. 11 May, 2018 5 commits
  14. 08 May, 2018 1 commit
  15. 05 May, 2018 2 commits
  16. 04 May, 2018 3 commits
  17. 03 May, 2018 2 commits
  18. 02 May, 2018 5 commits
  19. 01 May, 2018 1 commit
    • Benjamin Kaduk's avatar
      Fix regression with session cache use by clients · bf87bf45
      Benjamin Kaduk authored
      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: default avatarMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5967)
      
      (cherry picked from commit c4fa1f7f)
      bf87bf45