RE: [Skunkdav-dev] SSL connection problem

[GARTRELL,MIKE (HP-Corvallis,ex1) <mik...@hp...>]

	This problem was due to the cacerts file being in the wrong
location.  HTTPClient was was unable to find the proper certificate for the
server, which caused the NullPointerException described below.

	Will the next release of SkunkDAV formally license the DAV client
library portion under the LGPL?

-----Original Message-----
From: Jacob Smullyan [mailto:smu...@sm...]
Sent: Friday, February 01, 2002 6:19 PM
To: GARTRELL,MIKE (HP-Corvallis,ex1)
Cc: 'sku...@li...'
Subject: Re: [Skunkdav-dev] SSL connection problem


On Fri, Feb 01, 2002 at 05:39:45PM -0800, GARTRELL,MIKE (HP-Corvallis,ex1)
wrote:
> 	The NullPointerException is occuring inside the test
> (checkCertificate()), so yes, the test is failing.  Do you know what would
> cause this?  It appears there is a certificate problem on the client, but
I
> am unable to identify the root cause.  The appropriate certificate for the
> server that I'm connecting to is located in the keystore and the cacerts
> keystore.

But all the code in checkCertificate is enclosed in a try/block; why
would it cause the test to fail?  It is simply printing the stack
trace of the exception.  If the test is failing, it is for another
reason (probably the same reason that SSLSocket.getSession() is
returning null).  If the certificate is located in the keystore, then
I don't currently know why.  

I am currently upgrading the library to use the newer version of
HTTPClient.  I just looked at the SSL patches used by Joachim Feise's
DAVExplorer, which also uses HTTPClient.  You might try a simple
connection test to your server with my HTTPClient patch and with
Feise's; my patch is taken from Tschalar's, and is rather crude.  I'd
be delighted if Feise's worked for you; his code and mine are
license-compatible, and I could incorporate his patch or some portion
thereof.

> 
> -----Original Message-----
> From: Jacob Smullyan [mailto:smu...@sm...]
> Sent: Friday, February 01, 2002 4:52 PM
> To: GARTRELL,MIKE (HP-Corvallis,ex1)
> Cc: 'sku...@li...'
> Subject: Re: [Skunkdav-dev] SSL connection problem
> 
> 
> On Fri, Feb 01, 2002 at 04:10:44PM -0800, GARTRELL,MIKE (HP-Corvallis,ex1)
> wrote:
> > 	I'm receiving the following exception when attempting to establish
> > an HTTPS connection to a DAV server using SkunkDAV 1.0.2.4:
> > 
> > .java.lang.NullPointerException
> >         at
> > HTTPClient.jsse.JsseSSLSupport.checkCertificate(JsseSSLSupport.java:91)
> >         at
> > HTTPClient.jsse.JsseSSLSupport.createSocket(JsseSSLSupport.java:73)
> >         at
HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:2846)
> >         at
> HTTPClient.HTTPConnection.handleRequest(HTTPConnection.java:2662)
> >         at
> HTTPClient.HTTPConnection.setupRequest(HTTPConnection.java:2455)
> >         at
> > HTTPClient.HTTPConnection.ExtensionMethod(HTTPConnection.java:1315)
> >         at
> > org.skunk.dav.client.DAVConnection.execute(DAVConnection.java:221)
> >         at com.hp.vdpcore.webdav.DAVWriter.writeFile(Unknown Source)
> >         at
> >
>
com.hp.vdpcore.webdav.test.DAVWriterTest.testWriteFile(DAVWriterTest.java:11
> > 7)
> >         at java.lang.reflect.Method.invoke(Native Method)
> >         at junit.framework.TestCase.runTest(TestCase.java:156)
> >         at junit.framework.TestCase.runBare(TestCase.java:130)
> >         at junit.framework.TestResult$1.protect(TestResult.java:106)
> >         at junit.framework.TestResult.runProtected(TestResult.java:124)
> >         at junit.framework.TestResult.run(TestResult.java:109)
> >         at junit.framework.TestCase.run(TestCase.java:121)
> >         at junit.framework.TestSuite.runTest(TestSuite.java:157)
> >         at junit.framework.TestSuite.run(TestSuite.java:152)
> >         at junit.textui.TestRunner.doRun(TestRunner.java:74)
> >         at junit.textui.TestRunner.run(TestRunner.java:201)
> >         at
> > com.hp.vdpcore.webdav.test.DAVWriterTest.main(DAVWriterTest.java:97)
> > 
> >     	The above occurs when executing a PUT using the PutMethod.
Any
> > ideas about what might cause this?
> 
> The stack trace is getting printed, but not passed up to the caller,
> right?  I don't see any other possibility in that method.
> 
> The method in question is rather pointless to begin with at the
> moment.  It doesn't do anything, actually, except possibly print an
> error message of one kind or another.   Does the test fail?
> 
> j
> 
> \>  
> > 
> > ---> Mike Gartrell <---     ---> mik...@hp... <---
> >                             ---> phone: (541) 715-0008 <---
> > 
> > 
> > _______________________________________________
> > Skunkdav-dev mailing list
> > Sku...@li...
> > https://lists.sourceforge.net/lists/listinfo/skunkdav-dev
> 
> -- 
> Jacob Smullyan | smu...@sm...
> http://www.smullyan.org/smulloni/
> 
> _______________________________________________
> Skunkdav-dev mailing list
> Sku...@li...
> https://lists.sourceforge.net/lists/listinfo/skunkdav-dev

-- 
Jacob Smullyan | smu...@sm...
http://www.smullyan.org/smulloni/