You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bcprov-jdk15on-1.69.jar not works with JDK 8 -- 8u331 #1252
-- Create keystores by using keytool command from 8u261, 8u291 and 8u331
-- Test them with ssl debug all and security debug all enabled on client.
-- Replication Steps :
Do a 2 way ssl connections - successful.
Trigger a soap service to load BC into the JVM
Redo step#1. eg do another 2 way ssl connection -- this time it failed.
-- Test result of using different JDK8 version. #1: 8u261: work #2: 8u291: work #3: 8u331: fail
For case #3:
-- In the test case, the first JSSE client test actually works successfully.
-- Only after the BounceCastle is loaded, the JSSE client becomes failed.
-- It's because this 8u331 keystore was created (by 8u331 keytool command) with new algorithm PBEWithHmacSHA256AndAES_256 which is not supported by Bouncy Castle.
-- The spec from BC shows that: https://www.bouncycastle.org/specifications.html
-- Look at the JCE Provider session, and this algorithm is not listed in the specs.
-- In the 2nd SSL connection, BC fails and falls back to SunJCE.
-- SunJCE fails to find the private key.
SunJCE failed to find the private key may be a different issue.
Question: how can BC keeps up with JDK new security changes. So things will not break.
Closing this as it's not a bug (although it may turn into one). As you say, we can't be responsible for changes made in the JVM after we've released a version, but you do realize we're now at 1.72?
Closing this as it's not a bug (although it may turn into one). As you say, we can't be responsible for changes made in the JVM after we've released a version, but you do realize we're now at 1.72?
We have tried 1.72 and issue persistent. As long one use 2 ways SSL and loaded BC into JVM... 2 ways SSL no longer works.
We also logged a bug against JDK Security team as well. Not sure how to position if we are the user on this case.
Activity
dghgit commentedon Oct 24, 2022
Closing this as it's not a bug (although it may turn into one). As you say, we can't be responsible for changes made in the JVM after we've released a version, but you do realize we're now at 1.72?
wei-kumar commentedon Oct 31, 2022
We have tried 1.72 and issue persistent. As long one use 2 ways SSL and loaded BC into JVM... 2 ways SSL no longer works.
We also logged a bug against JDK Security team as well. Not sure how to position if we are the user on this case.