On Tue, 2010-12-14 at 11:51 +0100, Gerhard Sinne wrote:
> > > main, WRITE: TLSv1 Alert, length = 2
> >
> > Gerd
> >
> > This looks like a SSL protocol compatibility issue. Try using a
> > different version of the protocol (SSLv1 or TLSv1) and see if that makes
> > any difference.
>
> I inspected the CURL verbose output to see what SSL version was
> successfull.
> CURL says
> ...
>
> * SSLv3, TLS handshake, Finished (20):
> * SSL connection using AES128-SHA
> ...
>
> So I tried "SSLv3" first.
>
> SSLContext ctx = SSLContext.getInstance("SSLv3");
> MyTrustManager tm = new MyTrustManager();
> ctx.init (null, new MyTrustManager []{tm}, null);
> SSLSocketFactory socketFactory = new SSLSocketFactory(ctx);
>
> No way.
> Also tried
> TLS
> TLSv1/2
> SSLv1/2/3
> So all in all no difference. Problem persists.
>
> While debugging and inspecting the contents of classes, I found something
> appearing suspicious to me:
> After execution of the code section above,
> "ctx.contextSpi.trustManager" and
> "socketFactory.socketFactory.trustManager" both point to
> "com.sun.net.ssl.internal.ssl.DummyX509TrustManager"
>
> I would expect my "MyTrustManager" to appear in the socketFactory at that
> point.
>
>
> Regards
> Gerd
>
Gerd,
I have run out of ideas.
If you can reproduce the problem with a test app that can be executed
outside your local environment I'd happily take a look at it.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
