On Feb 1, 2006, at 12:43 PM, Tom Tromey wrote:
I'd like some comments before checking this in.
According to the JCE guide, a security provider can be loaded via the
class path, see:
http://java.sun.com/j2se/1.5.0/docs/guide/security/jce/
JCERefGuide.html#InstallProvider
This means that the provider should be loaded using the system class
loader, not the bootstrap class loader. This patch implements this
change.
I think this is correct, and I do remember seeing a problem on one VM
(I don't remember which) where it couldn't load GNU Crypto or Jessie
(before the merge) because their Jar files weren't in the boot
classpath.
Are there any permissions needed to do this? Does this need to be
wrapped in a PrivilegedAction?
