Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36942

Differentiate invalid hostname from invalid certificate

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.3, 4.1.3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Minor Change
    • ALL
    • v4.0
    • Platforms 2018-09-10
    • 0

      SecureTransport implementation currently treats ::kSecTrustResultRecoverableTrustFailure as an invalid hostname signal, however other trust failures could cause it.
      Since there's no way to clearly tell what the recoverable trust failure was, fall back on not setting the peer name (similar to C-driver's implementation) when the setting is applied.

            Assignee:
            sara.golemon@mongodb.com Sara Golemon
            Reporter:
            sara.golemon@mongodb.com Sara Golemon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: