Issues after 8u282 -> 8u292 update: "NoSuchAlgorithmException: unrecognized algorithm name: PBEWithSHA1AndDESede"

[lutkerd]

An issue has been reported by users of BouncyCastle, after upgrading from 8u282 or earlier to 8u292, a "NoSuchAlgorithmException: unrecognized algorithm name" exception is thrown at runtime. This issue will be fixed in the next release 8u302 which is expected on 7/19.

Workarounds:
There are 2 few possible workarounds, the 1st is preferred if it works for your application.

1. Call "new EncryptedPrivateKeyInfo("PBEWithSHA1AndDESede", new byte[] { 0 });" from your code as early as possible before any BouncyCastle jars are loaded.

2. Clear out the algorithms so they are reinitialized on next call using something like this

    public static void clearAlgorithms() {
        try {
            Class<?> clazz = sun.security.x509.AlgorithmId.class;
            java.lang.reflect.Field f1 = clazz.getDeclaredField("oidTable");
            f1.setAccessible(true);
            f1.set(clazz, null);
            java.lang.reflect.Field f2 = clazz.getDeclaredField("initOidTable");
            f2.setAccessible(true);
            f2.set(clazz, false);
        } catch (Exception e) {
            System.out.println(e);
            e.printStackTrace();
        }
    }

Root Cause Analysis:
There was a change in the upstream OpenJDK to improve JARs verification, which caused the list of Algorithms be to cached with only a subset of the SecurityProviders enabled. When an algorithm from SunJCE or BouncyCastle is requested the table is not refreshed and a NoSuchAlgorithmException is being thrown.

Additional information:
bcgit/bc-java#941
https://bugs.openjdk.java.net/browse/JDK-8266929

[lutkerd]

This was resolved in 8u302.