-
Enhancement
-
Resolution: Fixed
-
P3
-
6
-
b78
-
generic
-
generic
The following forum thread mentions a problem when trying to use the BC implementation as the primary JCE provider.
http://forum.java.sun.com/thread.jspa?threadID=702083&tstart=0
This was also reported as webbug:
``When attempting to dynamically register a JCE provider, that provider cannot be registered too high up in the search order due to a bug in the Sun JVM. This bug has been duplicated on both Mac OS X and Windows 2000, XP. It was registered with Apple as Java Bug #3294108 (JCE Providers Crash with Bus Error) and with Sun's Java Developer Connection underJDC Review ID 188804 (Dynamic Registration of JCE Provider in Position 1 Results in Stack Overflow). If your code is going to employ a dynamic registration strategy, do not place your JCE provider of choice in position 1 without checking if Sun has closed this bug first!" - Weiss, Jason (2004) Java Crytpography Extensions. Morgan Kaufmann. pp11-12.
For some reason, this webbug was closed as "too old", which makes no sense to me.
We should understand why. Do we not have an keyUsage in place that BC is requiring for certificate verification? Might be a problem in testSignatures().
http://forum.java.sun.com/thread.jspa?threadID=702083&tstart=0
This was also reported as webbug:
``When attempting to dynamically register a JCE provider, that provider cannot be registered too high up in the search order due to a bug in the Sun JVM. This bug has been duplicated on both Mac OS X and Windows 2000, XP. It was registered with Apple as Java Bug #3294108 (JCE Providers Crash with Bus Error) and with Sun's Java Developer Connection underJDC Review ID 188804 (Dynamic Registration of JCE Provider in Position 1 Results in Stack Overflow). If your code is going to employ a dynamic registration strategy, do not place your JCE provider of choice in position 1 without checking if Sun has closed this bug first!" - Weiss, Jason (2004) Java Crytpography Extensions. Morgan Kaufmann. pp11-12.
For some reason, this webbug was closed as "too old", which makes no sense to me.
We should understand why. Do we not have an keyUsage in place that BC is requiring for certificate verification? Might be a problem in testSignatures().