jessie-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Anders Biehl Nørgaard
Subject: Re: [Jessie-discuss] Problems using Jessie as sun jdk drop-in
Date: Thu, 1 Jul 2004 21:27:45 +0200 (CEST)

Hi Casey,


Thanks for the reply - after restoring

#
# List of providers and their preference orders (see above):
#
security.provider.1=org.metastatic.jessie.provider.Jessie
security.provider.2=sun.security.provider.Sun

#security.provider.1=sun.security.provider.Sun
#security.provider.2=com.sun.net.ssl.internal.ssl.Provider


I got

------------
D:\eclipse_ws\HttpMonitor_config>"C:\java\j2sdk1.4.1_05\bin\java"
-Djavax.net.debug=all -DproxySet=true -Dhttp.proxyHost=10.255.237.7
-Dhttp.proxyPort=8887 -Dhttps.proxyHost=10.255.237.7
-Dhttps.proxyPort=8887 -cp
gnu-crypto.jar;jessie.jar;D:\eclipse_ws\HttpMonitor RunScenario -v
new_scenarios_maj2004/eBL_login.scenario
java.lang.RuntimeException
java.lang.RuntimeException: Export restriction: SunJSSE only
        at javax.net.ssl.SSLContext.getSocketFactory(Unknown Source)
        at
        
httpsequencer.propertyscript.ScenarioReader.readSSLFactory(ScenarioReader.java:208)
        at
        httpsequencer.propertyscript.ScenarioReader.read(ScenarioReader.java:98)
        at RunScenario.runScenario(RunScenario.java:122)
        at RunScenario.main(RunScenario.java:54)
---------

and after prepending to the bootclasspath I got further....but not far

----------

D:\eclipse_ws\HttpMonitor_config>"C:\java\j2sdk1.4.1_05\bin\java"
-Djavax.net.debug=all -DproxySet=true -Dhttp.proxyHost=10.255.237.7
-Dhttp.proxyPort=8887 -Dhttps.proxyHost=10.255.237.7
-Dhttps.proxyPort=8887 -Xbootclasspath/p:gnu-crypto.jar;jessie.jar -cp
D:\eclipse_ws\HttpMonitor RunScenario -v
new_scenarios_maj2004/eBL_login.scenario

java.lang.RuntimeException
java.lang.RuntimeException: Export restriction: this JSSE implementation
is non-pluggable.
        at
        com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.checkCreate(Unknown 
Source)
        at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown
        Source)        at
        
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown 
Source)
        at
        sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
        Source)
        at
        sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown
        Source)
        at
        
sun.net.www.protocol.https.HttpsURLConnectionImpl.getHeaderField(Unknown Source)
        at
        
httpsequencer.ScenarioAssignment.createHeader(ScenarioAssignment.java:544)
        at
        
httpsequencer.SimpleResponseHandler.sendRequest(SimpleResponseHandler.java:413)
        at
        httpsequencer.ScenarioAssignment.advance(ScenarioAssignment.java:330)
        at RunScenario.runScenario(RunScenario.java:129)
        at RunScenario.main(RunScenario.java:54)


Do you think I will have better luck with Kaffe 1.1.4 on linux? Any other
ideas? (Any Sun JDK's that are not export restricted?) Maybe IBM's JDK?

Thanks
Anders



>>>>>> "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







reply via email to

[Prev in Thread] Current Thread [Next in Thread]