Uploaded image for project: 'Harmony'
  1. Harmony
  2. HARMONY-6248

[classlib][security] Wildcard subjectAltName dNSName entries throw IOException

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 5.0M11
    • Classlib
    • None

    Description

      Using the DRLCertFactory JCE provider, calling getSubjectAlternativeNames() on an X509Certificate throws IOException if the subjectAltName extension in the certificate contains a dNSName entry with a wildcard (such as "*.example.com").

      This is ultimately because GeneralName::checkDNS() does not allow wildcard entries. RFC3280 and RFC1034 both discuss wildcards, although a strict reading of RFC3280 would appear not to allow for them in a subjectAltName dNSName. However, RFC3280 explicitly allows for application-specific semantics of use of wildcards in subjectAltName. As the Harmony code currently stands, it is not possible for an application to even retrieve the subjectAltName values if they contain a dNSName that does not strictly conform to the "preferred name syntax" in RFC1034. So it is not possible for an application to make the decision on what semantics to apply to a wildcard value.

      Attachments

        1. harmony-6248.patch
          0.9 kB
          Tim Ellison
        2. harmony-6248-v2.patch
          1 kB
          Tim Ellison

        Activity

          People

            tellison Tim Ellison
            scytmo Ian Payton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: