Re: [rtcweb] Security architecture: Making ECDSA mandatory

Sean Turner <sean@sn3rd.com> Thu, 09 June 2016 17:29 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D954412D8DA for <rtcweb@ietfa.amsl.com>; Thu, 9 Jun 2016 10:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 Yls9o3TSxRvX for <rtcweb@ietfa.amsl.com>; Thu, 9 Jun 2016 10:29:27 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4803512D789 for <rtcweb@ietf.org>; Thu, 9 Jun 2016 10:29:27 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id i187so24509829qkd.3 for <rtcweb@ietf.org>; Thu, 09 Jun 2016 10:29:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=L9LntyoSB7DGDY1vgm/6B0mMb4hXPKP5tBxo2byfmXA=; b=RuTCKC2DCaiykNH9Gm5iDX8Z2y3+SQHKn3tAk++EmGGMtU/L6DuFRgXLClcj9u5kly W2pc0ZyqdrGHMamKvN6GzbYgViLYE3bFpCuNcJxGRwV+yA8C2gPjEafxt132ikY9C0e+ cak0sQ6t1Bip8GqnPXnylyhPHgTVTa6AY47UQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=L9LntyoSB7DGDY1vgm/6B0mMb4hXPKP5tBxo2byfmXA=; b=MHdgdAK11DHI4W6d3jGRlsQPyVLaQ/2+4nStkV1a9spLKQP0tN2szfmONSmyZgk1Ge 0PtRl2H38FQRj0nNQn0+0hTaYqpnadAyvCUtn0YZ3mJErUgj4bxLy/GNiKB/TRWM0yLI DiIdTGk5iwjDzAKh4WpWfn44KtXTSRRbkGJc86NQqsnv7BVWvdIUSIogbpRdzh9520Mw eltD6ogqDLrItjSygZ9aqhPHhzmWF6H9xUXLlt/waiscYXaDcvou1RT2BeT2nwyzFZMB pD3lfjVm4crvHMU81vFEazS/++gRzYgZf1M2Lxo50G4thFS+nr+ZST31uTDpDIs8SxPs 0/tw==
X-Gm-Message-State: ALyK8tIyWGl5WZU8zFWiC1HWD7YByL2eht+NdvL2NacM3H/W+3XO7TSdTl5sp3uADwwpWQ==
X-Received: by 10.55.144.68 with SMTP id s65mr10984153qkd.209.1465493366323; Thu, 09 Jun 2016 10:29:26 -0700 (PDT)
Received: from [5.5.33.201] (vpn.snozzages.com. [204.42.252.17]) by smtp.gmail.com with ESMTPSA id h132sm1918666qhh.32.2016.06.09.10.29.25 for <rtcweb@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 09 Jun 2016 10:29:25 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <3A4427FF-A0F1-4B1A-B30C-7FE4319515A2@gmail.com>
Date: Thu, 9 Jun 2016 12:29:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B7A187E-D85C-4EB7-A4A8-221E1FD5E059@sn3rd.com>
References: <CABkgnnWjaBqVdNurt+sd3w9U_rpTi0WJKFce12KfA2W1mrnsTA@mail.gmail.com> <57457874.1010708@alvestrand.no> <3A4427FF-A0F1-4B1A-B30C-7FE4319515A2@gmail.com>
To: rtcweb@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/8ZokyJ5dv7vvaDjBCVbL6T2xy5w>
Subject: Re: [rtcweb] Security architecture: Making ECDSA mandatory
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2016 17:29:29 -0000

I believe it’s in the newly posted -12 version:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-security-arch

spt

> On Jun 09, 2016, at 10:08, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> 
> It should be merged. 
> 
> On May 25, 2016, at 03:03, Harald Alvestrand <harald@alvestrand.no> wrote:
> 
>> In my search for status on ECDSA (we're in the process of switching the Chrome default), I came across this in the current draft:
>> 
>>    All implementations MUST implement DTLS 1.0, with the cipher suite
>>    TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA and the DTLS-SRTP protection
>>    profile SRTP_AES128_CM_HMAC_SHA1_80.  Implementations SHOULD
>>    implement DTLS 1.2 with the TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
>>    cipher suite.  Implementations SHOULD favor cipher suites which
>>    support PFS over non-PFS cipher suites and GCM over CBC cipher
>>    suites.  [[OPEN ISSUE: Should we require ECDSA?  Waiting for WG
>>    Consensus.]]
>> 
>> 
>> I also found Martin's PR. It's 11 months old, still open.
>> 
>> Can we merge this now?
>> 
>> 
>> On 06/13/2015 12:06 AM, Martin Thomson wrote:
>>> I've opened https://github.com/rtcweb-wg/security-arch/pull/33
>>> 
>>> 
>>> This changes the MTI cipher suites to ECDSA and does a little cleanup
>>> on the corresponding API requirements to more closely match what has
>>> just landed in the W3C specification.
>>> 
>>> We discussed ECDSA and the only concerns raised were with
>>> compatibility.  I've done some testing with other implementations with
>>> no issues, and ECDSA seems to be well supported on all those
>>> hard-to-upgrade PSTN gateways (thanks to Cullen and Ethan for helping
>>> out with checks there and to NIST for creating certification pressure
>>> with FIPS-2).
>>> 
>>> I have an implementation that switches Firefox to ECDSA with P-256 by
>>> default.  It's much, much faster.  
>>> http://bench.cr.yp.to/
>>>  claims that
>>> it's 150 times faster on mobile devices for keygen.
>>> 
>>> _______________________________________________
>>> rtcweb mailing list
>>> 
>>> rtcweb@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb