Interestingly enough, I can dynamically load the BC provider if I place the jar in the $JAVA_HOME/lib/ext directory, but it certainly doesn't want to load (properly) from anywhere else ($JBOSS_HOME/lib, $JBOSS_HOME/server/default/lib, $JBOSS_HOME/server/default/deploy/jboss-net.sar).

On Feb 2, 2004, at 9:33 AM, Jason Essington wrote:


On Feb 1, 2004, at 6:58 AM, Scott M Stark wrote:


I have not tried this, but others said they have done it.

Then I certainly must be doing something wrong


Where are you putting the jar

In the jboss-net.sar along with other Web Service Security support libraries.


and how is the BouncyCastle provider being installed?

In a static initializer the following code is called:
java.security.Security.addProvider(new org.bouncycastle.jce.provider.BouncyCastleProvider());


This code doesn't throw any exception, so the jar containing the provider is found just fine.
but later when an attempt is made to access a cypher (RSA) that is supplied by BC using the code:
cipher = Cipher.getInstance("RSA");
yields an exception saying something about no provicer for that cipher, however calling
cipher = Cipher.getInstance("RSA", "BC");
basically forcing the use of the Bouncy castle provider, yields the previously mentioned SecurityException.



Should I be adding the provider in a different way, or perhaps from a different place?


-jason




xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Essington Sent: Friday, January 30, 2004 3:47 PM To: [EMAIL PROTECTED] Subject: [JBoss-dev] Adding JCE providers at runtime.

I am trying to add the BouncyCastle Security Provider at runtime. The
call to java.security.Security.addProvider() seems to succeed, but later
attempts to use the provider cause a SecurityException with the message
"The provider BC may not be signed by a trusted party". This jar works
fine from command line apps, and if it is installed in the jre (jar
added to the lib/ext dir and an entry made into the java.security file),
so there is no problem in the signed jar.


Is this maybe a classloader problem where java.security can't find the
cacerts file to verify the jar? What else could be causing the problem?


-jason




------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development


-jason



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to