Uploaded image for project: 'Openfire'
  1. Openfire
  2. OF-1377

Openfire's self-signed certificates cause troubles in Android clients

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: TLS

      Description

      Can't reproduce this with Xabber on my local test server, but some users report troubles using Openfire's own generated certificates. A quote from Github issue on Xabber (Android) page:

      The self signed certificates created by OpenFire will crash the Java/Android TLS stack when accessing getSubjectAlternativeNames() on the the peer certificate.
      This usually goes unnoticed in other applications since the DefaultHostnameVerifier checkes the CN first. That however is a violation of RFC6125 section 6.4.4 which requires us to check for the existence of SAN first.

        Attachments

          Activity

            People

            Assignee:
            dwd Dave Cridland
            Reporter:
            wroot wroot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: