Re: [rtcweb] Open Security issue: Crypto algorithms

Ted Hardie <ted.ietf@gmail.com> Thu, 07 May 2015 09:38 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF3F1A0068 for <rtcweb@ietfa.amsl.com>; Thu, 7 May 2015 02:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 yustmkAHQuiC for <rtcweb@ietfa.amsl.com>; Thu, 7 May 2015 02:38:39 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (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 998F11A0067 for <rtcweb@ietf.org>; Thu, 7 May 2015 02:38:38 -0700 (PDT)
Received: by wgin8 with SMTP id n8so37595701wgi.0 for <rtcweb@ietf.org>; Thu, 07 May 2015 02:38:37 -0700 (PDT)
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=/1OlfT3UHqZIqswxap3mubyRxw0F+cgu6o/5LFaMZFM=; b=I9GE6iofmmhd7l2BhPBCR+G6vfHltJ+BPPvugoGClueZ4yqYamlrgFZwB6OkVazCvT Ul6o/n5igqlamrf1kEsVgpPCa8mTdhGEkv1jE3YMdNeNqDyJBaTjxIJ4DC8EvKOHpRuR DAH+WLC06pGwkWo1hsh9OL8ioWAquqby3rRgy0Z08zEGucxSYnmHdhulNzMkSXRIG0cB /26CZJzQFdA4OsfAZu/4PQuXaat6qUL8i7G3OMoZSQHFxJRlc/O98dKw/m57RqPlac5p PDqa1J+y8cMn246/z8qkkKfsfoeaMyjiSGnkm7VOFqp8AeNAc/L3vZ01PFHD4xRBQcd3 qblQ==
MIME-Version: 1.0
X-Received: by 10.180.87.101 with SMTP id w5mr4988598wiz.18.1430991517335; Thu, 07 May 2015 02:38:37 -0700 (PDT)
Received: by 10.194.233.233 with HTTP; Thu, 7 May 2015 02:38:37 -0700 (PDT)
In-Reply-To: <CABkgnnUquwQVo+RO=96UVBVuJ-EhZQzsCA6vV7LBbEpCiGS=bQ@mail.gmail.com>
References: <5549E480.4030806@alvestrand.no> <CABkgnnUquwQVo+RO=96UVBVuJ-EhZQzsCA6vV7LBbEpCiGS=bQ@mail.gmail.com>
Date: Thu, 07 May 2015 10:38:37 +0100
Message-ID: <CA+9kkMAOu28ZmBPv2vPjU5EQsGF2isgMuw_KUKKroJ-P3Fn_LA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="f46d044402e411496605157aad93"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/DvK0c317WFybWDGeti63BdmbGvY>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Open Security issue: Crypto algorithms
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 07 May 2015 09:38:40 -0000

I am not chair with the particularly good position to collect feedback, but
I happen to know he's flying today.  My understanding of the current theory
is that we ask TLS what cipher suites and version numbers to mandate; if we
had a strong reason to disagree, we would need to document why we went with
something other than what they suggested.

He-who-is-in-the-air may tell me I've got it wrong, of course.

Ted

On Wed, May 6, 2015 at 4:58 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 6 May 2015 at 02:53, Harald Alvestrand <harald@alvestrand.no> wrote:
> > Do we have an idea on how to move forward with resolving the outstanding
> > question?
>
> I would like to make ECDSA mandatory.  There seems to be no question
> regarding ECDHE.  We intend to implement ECDSA, but need the
> certificate management API additions so that we can avoid
> compatibility issues (I'll note that chrome and firefox are perfectly
> happy to negotiate ECDSA with anyone who chooses to use it today, but
> there might be some gateway/server code out there that might not
> tolerate it as readily).
>
> We can ask TLS, but I will defer to the chairs on how they want to
> collect feedback (one of the chairs is in a particularly good position
> in this respect, I note).
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>