PKCS#8 multi-prime RSA keys lose multi-prime and CRT components upon private key creation

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: P4
    • None
    • Affects Version/s: 8, 11, 17, 21
    • Component/s: security-libs
    • None

      When creating RSA keys from a PKCS#1 or PKCS#8 encoding that involves OtherPrime information (meaning more than two primes is used to create the modulus), the resulting key is an RSAPrivateKeyImpl. While this works fine and n and d are used during private key operations, it discards the usual CRT components as well as the OtherPrime info, making it impossible to move to another provider that does support multi-prime RSA.

      The encoded data from this kind of key then populates zero values for the CRT components and loses all OtherPrime elements.

            Assignee:
            Jamil Nimeh
            Reporter:
            Jamil Nimeh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: