Path: csiph.com!x330-a1.tempe.blueboxinc.net!aioe.org!feeder.news-service.com!feeder.erje.net!news2.arglkargh.de!news.n-ix.net!news.belwue.de!rz.uni-karlsruhe.de!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail
From: Lothar Kimmeringer <news200709@kimmeringer.de>
Newsgroups: comp.lang.java.programmer
Subject: Re: SSL client program
Date: Sun, 15 May 2011 13:52:41 +0200
Organization: Organization?! Only chaos here!
Lines: 25
Message-ID: <o36z94keqaxr.dlg@kimmeringer.de>
References: <3af63731-b09e-44ff-bf37-1ffebdf80f60@o7g2000vbn.googlegroups.com>
Reply-To: news@kimmeringer.de
NNTP-Posting-Host: mnch-4d043d4f.pool.mediaways.net
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Trace: online.de 1305460361 19086 77.4.61.79 (15 May 2011 11:52:41 GMT)
X-Complaints-To: abuse@einsundeins.com
NNTP-Posting-Date: Sun, 15 May 2011 11:52:41 +0000 (UTC)
User-Agent: 40tude_Dialog/2.0.15.1de
Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4110

Stone wrote:

> 24741:error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version
> number:s3_pkt.c:295:
> 
[...]
>             sslContext = SSLContext.getInstance("SSLv3");

I filed a bugreport about two years ago showing that the JSSE is
creating TLSv1-messages in some circumstances but since this falled
within the Oracle-takeover of SUN it seems that it has been ignored.

To find out if this specific bug is biting here, start Wireshark
and listen to the packets being exchanged between your client and
the server. The client-hello message is unencrypted, so it should
be easy to see what version is sent to the server.


Regards, Lothar
-- 
Lothar Kimmeringer                E-Mail: spamfang@kimmeringer.de
               PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81)

Always remember: The answer is forty-two, there can only be wrong
                 questions!