Re: [TLS] issues with DTLS + PSK

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 05 January 2015 18:47 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F631A87D9 for <tls@ietfa.amsl.com>; Mon, 5 Jan 2015 10:47:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VwDm6MHv7XXB for <tls@ietfa.amsl.com>; Mon, 5 Jan 2015 10:47:17 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B99131A6FEB for <tls@ietf.org>; Mon, 5 Jan 2015 10:47:16 -0800 (PST)
Received: from [192.168.131.143] ([80.92.122.140]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0LngNT-1Xbrnw3dPD-00hxzK; Mon, 05 Jan 2015 19:47:08 +0100
Message-ID: <54AADC2A.2050202@gmx.net>
Date: Mon, 05 Jan 2015 19:47:06 +0100
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <1420474094.10168.49.camel@redhat.com> <54AAD743.6070801@gmx.net> <CABkgnnUEiVp=gXrFSS=JmGh8wJy-zN3=3U1ff-+fEZvazUWj=w@mail.gmail.com>
In-Reply-To: <CABkgnnUEiVp=gXrFSS=JmGh8wJy-zN3=3U1ff-+fEZvazUWj=w@mail.gmail.com>
OpenPGP: id=4D776BC9
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="65gIPlmcju1NKQIL2tspDb39Wst7XJVvH"
X-Provags-ID: V03:K0:A23VCV76aB3jGGL9fZopEaXK9k12odtqP2YG1qmypXmoILE3EzF 1i05RwH2GpWuT0edie0xa17W7WsktkmlnFY/sJzr5pO7cbCv7WZQXxBGxUKyYg4yF35rU/D IC+eXzePVThdjy/yo3GvAKsxcOMiLzZViZhHGuWMK4sjZD3tl9+EfMoXSsciEipy1n1ymii MxTsDIUsbhFC4U0XrSuRA==
X-UI-Out-Filterresults: notjunk:1;
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/l6zBcqzeeAtMboS9aTNFW509tac
Cc: IETF TLS <tls@ietf.org>
Subject: Re: [TLS] issues with DTLS + PSK
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 18:47:20 -0000

Hi Martin,

I was talking about PSK is used today in DTLS 1.2. Of course, in the
future (with TLS/DTLS 1.3) it might look differently and approach
mentioned below with #1 makes sense to me.

Ciao
Hannes


On 01/05/2015 07:41 PM, Martin Thomson wrote:
> On 5 January 2015 at 10:26, Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
>> Using DTLS-PSK in combination with DH is IMHO not particularly useful
>> since then you can also switch to a raw public key right away since you
>> loose all the performance and code size benefits that the PSK mechanism
>> provides with DTLS.
> 
> 
> The theory that I've heard regarding this was that we might have two modes:
> 
> 1. A PSK that mapped directly into session resumption (i.e., you are
> "resuming" some non-existent session).
> 
> 2. A PSK that followed the full handshake with DH.
> 
> While the latter is certainly slow and expensive, I think it was
> Carsten who suggested that some IoT devices would be interested in -
> occasionally - doing an ephemeral handshake.  Forward secrecy was a
> desirable property, and some devices would be able to do the work as
> long it was infrequent and there were no time-critical functions in
> progress.
>