I'm having problems using the SunJCE cryptoprovider when located on the
classpath (non installed extension) and using static registration.
When used as an installed extension (jar files copied in <java-home>/lib/ext)
all runs smoothly.
My client is a simple command line interface that encrypts data with a DES
key, and picks up the static installed cryptoproviders :
> SUN (DSA key/parameter generation; DSA signing; SHA-1, MD5 digests;
SecureRandom; X.509 certificates; JKS keystore)
> SunJCE Provider (implements DES,Triple DES, Blowfish, PBE, Diffie-Hellman,
HMAC-MD5, HMAC-SHA1)
My Jboss server does not find the SunJCE provider, unless dynamically
included :
Security.addProvider(new com.sun.crypto.provider.SunJCE());
For the static include, I added all permissions needed (triple-checking
classpaths and location of the jar files) in the server.policy file, with
explicit use of the -Djava.security.policy command line argument, and later
as well in my jdk java.policy file, yet the SunJCE never gets included.
Anyone seen this before?
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
