Re: [TLS] issues with DTLS + PSK

Martin Thomson <martin.thomson@gmail.com> Mon, 05 January 2015 18:41 UTC

Return-Path: <martin.thomson@gmail.com>
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 D3EBE1A6FFB for <tls@ietfa.amsl.com>; Mon, 5 Jan 2015 10:41:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 mtBRt65vvVqo for <tls@ietfa.amsl.com>; Mon, 5 Jan 2015 10:41:18 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17E531A6FEB for <tls@ietf.org>; Mon, 5 Jan 2015 10:41:18 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id uy5so62311297obc.4 for <tls@ietf.org>; Mon, 05 Jan 2015 10:41:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mFNSppvvdxJVBfBWWYt2Dc9titd9YO0q7b+1FUGaA4k=; b=uZlP9dy3NgCKICbK0ODL4Y0GWfJqNff5YyY3/dHeN8ThKdaQu5Pm/T5OweFtI1mzul jUatQDv8mPGEb8NN/xnVNtIT2LK3ANMH9T0YCpsFL8DZngmBcX5Hyiz10BS4f2qFmCT7 ATaMuXpanaxNF3f4yeG7w7YK4JhUZwFXPsO+ws1cKmX9AYqbTNCHqnTh8g2Jrt4Cjv9e MYMEghjtLbkLjFW2lZaIuNgvTQsJuWxNM6oK+uNfKSdWlTe3XxmgQdzuAhz1b6lhEk2n ++O37wQOm3L33OAqIJB4mjLm2S3YXrOjq/u0mC7uYBG0M5mOhDp4Y2MFb097cVLePFWV za8g==
MIME-Version: 1.0
X-Received: by 10.60.145.167 with SMTP id sv7mr53763638oeb.38.1420483277333; Mon, 05 Jan 2015 10:41:17 -0800 (PST)
Received: by 10.202.226.136 with HTTP; Mon, 5 Jan 2015 10:41:17 -0800 (PST)
In-Reply-To: <54AAD743.6070801@gmx.net>
References: <1420474094.10168.49.camel@redhat.com> <54AAD743.6070801@gmx.net>
Date: Mon, 05 Jan 2015 10:41:17 -0800
Message-ID: <CABkgnnUEiVp=gXrFSS=JmGh8wJy-zN3=3U1ff-+fEZvazUWj=w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/XGuYrlnIb1_F_YK_SzuKZS85baM
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:41:20 -0000

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.