Re: [Jessie-discuss] Problems using Jessie as sun jdk drop-in

[Casey Marshall]

>>>>> "Anders" == Anders Biehl Nørgaard <address@hidden> writes:

Anders> Hi, I try to use jessie as a provider for SSL sockets as the
Anders> Sun-jsse seems to be defective for my purpose (communicating
Anders> through a NetScaler-box, http://www.netscaler.com/ , that
Anders> takes care of ssl - Suns jsse worked fine until the
Anders> NetScaler-box was added, Grr!)  Running on Win2k, sun
Anders> jdk1.4.1_05, I've edited my lib/security/java.security to
Anders> contain

Anders> # List of providers and their preference orders (see above): #
Anders> security.provider.1=org.metastatic.jessie.provider.Jessie
Anders> #security.provider.1=sun.security.provider.Sun
Anders> #security.provider.2=com.sun.net.ssl.internal.ssl.Provider
Anders> #security.provider.3=com.sun.rsajca.Provider
Anders> #security.provider.4=com.sun.crypto.provider.SunJCE
Anders> #security.provider.5=sun.security.jgss.SunProvider

You shouldn't comment out the `sun.security.provider.Sun' line, at
least. That provider has the "JKS" keystore. You should change the
number on that line to `2'.

You will run into trouble, too, once you try to load any JSSE class
that isn't Sun's. Sun has made their JSSE reject *any* pluggable JSSE
provider, so you will need to prepend Jessie's implementations of the
javax.net and javax.security.cert packages to your boot classpath.

Anders> But in the offending piece of code....

Anders> KeyStore ks= KeyStore.getInstance("JKS", new
Anders> org.metastatic.jessie.provider.Jessie()); // Filetype

Also this will not work. Jessie does not have a keystore
implementation. Once you have fixed your java.security file, this
alone should work:

  KeyStork ks = KeyStore.getInstance ("JKS");

Cheers,

-- 
Casey Marshall || address@hidden