Path: csiph.com!news.mixmin.net!aioe.org!.POSTED!not-for-mail
From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk>
Newsgroups: comp.lang.java.programmer
Subject: Re: writing a java clinent to support TLS 1.2
Date: Fri, 22 Jul 2016 19:33:41 -0400
Organization: Aioe.org NNTP Server
Lines: 16
Message-ID: <nmuagi$1oup$2@gioia.aioe.org>
References: <c626dacc-b027-43e3-9d1b-0e26a7d68dc1@googlegroups.com>
NNTP-Posting-Host: 7SK6yTFfqwlIPNBLl3l7Qg.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.lang.java.programmer:35098

On 7/21/2016 8:40 AM, mike wrote:
> We are writing a client in java that shall support TLS 1.2 when connecting to server. We will send NETCONF messages over this connection.
>
> It was quite easy to implement the support, just creating a SSLSocket.
>
> Any ideas on how to verify it?

Verify what?

Java has supported TLS 1.2 out of the box since Java 7.

You think Oracle got it wrong or?

Arne