IETF Logo Mail Archive

Re: [TLS] The PAKE question and PSK

Nico Williams <nico@cryptonector.com> Wed, 02 April 2014 17:35 UTC

Return-Path: <nico@cryptonector.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 D58E61A0326 for <tls@ietfa.amsl.com>; Wed, 2 Apr 2014 10:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.303
X-Spam-Level:
X-Spam-Status: No, score=0.303 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.347] autolearn=no
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 kOqdlPDA79Oy for <tls@ietfa.amsl.com>; Wed, 2 Apr 2014 10:35:34 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D73FF1A0318 for <tls@ietf.org>; Wed, 2 Apr 2014 10:35:34 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTP id 193E51B4059 for <tls@ietf.org>; Wed, 2 Apr 2014 10:35:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=zKYvcKLql6YbTpjuBAO3 ZIVt67U=; b=L3ng6LiNLkCTNx2jgmAzqg632CRxxlUQIGvWGxCnQyL2B7/ijckg OPrFBjsmsovepS/f6wAuBPmmwCpNbKbsxKOAcFQGJkZZ9haa7f/U0e+tEqnuH0MW S3b9Bgdem6c5js37Fu3BFSVDodrLyV09D/dfz+oWHOlHyE2Y8qu5Y8o=
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTPSA id C25DF1B4058 for <tls@ietf.org>; Wed, 2 Apr 2014 10:35:30 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id z2so5875427wiv.12 for <tls@ietf.org>; Wed, 02 Apr 2014 10:35:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.160.166 with SMTP id xl6mr3931437wib.42.1396460129424; Wed, 02 Apr 2014 10:35:29 -0700 (PDT)
Received: by 10.217.129.197 with HTTP; Wed, 2 Apr 2014 10:35:29 -0700 (PDT)
In-Reply-To: <CAK3OfOj7Wfo+BbTHfJGnEJE+OOs9ba43tFH24GX6rVWbf868iQ@mail.gmail.com>
References: <CACsn0cnBXvjo4cCN8htKvmakzhneqq4nXN9WfPdgkqjgBTNpGA@mail.gmail.com> <533BBC3C.6000704@gmx.net> <7a41ee191d22df1f5924a68034c74a49.squirrel@www.trepanning.net> <533C3D12.7040802@gmx.net> <3a1e30958a4e240be96d8a822a1fcdae.squirrel@www.trepanning.net> <CAK3OfOj7Wfo+BbTHfJGnEJE+OOs9ba43tFH24GX6rVWbf868iQ@mail.gmail.com>
Date: Wed, 02 Apr 2014 12:35:29 -0500
Message-ID: <CAK3OfOihs3V1AcZZmRCNsdk4snYWhXDqq8fGoNVCWv__gxf6OQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Dan Harkins <dharkins@lounge.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/qqXXnnvTnGDibrsmqCGGf6je_u0
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] The PAKE question and 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: Wed, 02 Apr 2014 17:35:39 -0000

With Elligator the eavesdropper goes from being able to eliminate
7/8ths of possible passwords with each exchange to being able to
eliminate only 19/2^256 possible passwords (in the curve25519 case;
the exact number varies by curve for which Elligator is available).
Therefore EKE with ECC + Elligator is safe.

v2.23.0 | Report a Bug | By Email