RE: [TLS] Re: Two notes on TLS 1.2 after implementing it in GnuTLS

Peter Williams <home_pw@msn.com> Sun, 10 December 2006 17:57 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtSvG-0002n9-Qx; Sun, 10 Dec 2006 12:57:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtSvF-0002mb-Iw for tls@lists.ietf.org; Sun, 10 Dec 2006 12:57:09 -0500
Received: from bay0-omc2-s33.bay0.hotmail.com ([65.54.246.169]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtSvE-0007re-1d for tls@lists.ietf.org; Sun, 10 Dec 2006 12:57:09 -0500
Received: from BAY103-W7 ([65.54.174.107]) by bay0-omc2-s33.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Sun, 10 Dec 2006 09:57:07 -0800
X-Originating-IP: [64.148.145.220]
X-Originating-Email: [home_pw@msn.com]
Message-ID: <BAY103-W74F8F4810ECF1D6672B3992D10@phx.gbl>
From: Peter Williams <home_pw@msn.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>, mike-list@pobox.com, tls@lists.ietf.org
Subject: RE: [TLS] Re: Two notes on TLS 1.2 after implementing it in GnuTLS
Date: Sun, 10 Dec 2006 09:57:07 -0800
MIME-Version: 1.0
X-OriginalArrivalTime: 10 Dec 2006 17:57:07.0341 (UTC) FILETIME=[9B7F23D0:01C71C84]
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc:
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2077282681=="
Errors-To: tls-bounces@lists.ietf.org

sounds more like they are using some or parts of the "SSL Handshake" (parts of which are now known as a "client protocols" of the TLS record layer, in a very dubious architectural move by IETF :-) given the SSL "privacy" goal) as a replacement for IKE, within the IPSEC architecture. 
 
I.E. there may be no TLS Record layer, in openVPN's application context ?
 
I can see why this will get the DARPA-funded folks in IETF jumping up and down, with rage; its dumps the (US-dominated) oakley compromises.
 
I don't believe this (i.e. merely) was an intended modality of the SSL patent, but _not_ inconsistent with the open-ness intended. N&S-derived handshakes for accessing network authentication servers have been around a fair while! I remember reading the article on the Cambridge design, when I was at school (20 years ago)!
 
WS-SX's SecureConversation is following the same course as OpenVPN we can note, however. They are paying careful attention paid to how T-bridges can be handled, each with different security policies concerning how handshakes are selected, the crypto module is seeded etc. It updates and nicely extends much of the unspecified/unstandardized work done in SSL Connect proxy land, with a strong focus on (a) multiple key management domains for each bridge segment, and (b) ensuring connectionless transports are properly handled (c) initiator/respondent access point roaming, and auto-rekeying of the cascade of T-bridge segments... upon roam of either endpoint (GSM security model, styled)
 
 



> From: pgut001@cs.auckland.ac.nz> To: home_pw@msn.com; mike-list@pobox.com; tls@lists.ietf.org> Subject: RE: [TLS] Re: Two notes on TLS 1.2 after implementing it in GnuTLS> Date: Mon, 11 Dec 2006 06:11:21 +1300> > Peter Williams <home_pw@msn.com> writes:> > >"OpenVPN actually runs TLS over UDP byimplementing a reliability layer for> >the TLS control channel. TLS is a fairlystrong, well regarded protocol,> >easily accessible using the OpenSSL library,and it seems to be the obvious> >choice for initial authentication and keyexchange. "> >http://sites.inka.de/bigred/archive/cipe-l/2003-09/msg00263.html> > In a nutshell what OpenVPN does is use TLS for the handshake and IPsec's ESP> for the UDP transport.> > >Is this still true? I'm proud of the designers who did this, if its true.> >They "got it' > > They certainly did. Throw away IKE and AH, and what's left of IPsec (ESP) is> actually pretty decent - they took the bits that worked and glued them> together to get... well, something else that works.> > Unfortunately the result is completely unpalatable to the IPsec folks, and> probably not too palatable for the TLS side either.> > Peter.
_________________________________________________________________
Search from any Web page with powerful protection. Get the FREE Windows Live Toolbar Today!
http://get.live.com/toolbar/overview
_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls