IETF Logo Mail Archive

Re: [rtcweb] JSEP fingerprint hash requirements

Martin Thomson <martin.thomson@gmail.com> Mon, 21 October 2013 17:58 UTC

Return-Path: <martin.thomson@gmail.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 7C8DE11E8361 for <rtcweb@ietfa.amsl.com>; Mon, 21 Oct 2013 10:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.234
X-Spam-Level:
X-Spam-Status: No, score=-2.234 tagged_above=-999 required=5 tests=[AWL=-0.234, BAYES_00=-2.599, J_CHICKENPOX_111=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id peLc36LIytl0 for <rtcweb@ietfa.amsl.com>; Mon, 21 Oct 2013 10:58:17 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id B6B2B11E825C for <rtcweb@ietf.org>; Mon, 21 Oct 2013 10:57:57 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id b13so4947293wgh.2 for <rtcweb@ietf.org>; Mon, 21 Oct 2013 10:57:56 -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=wRQF+2efBAPyu2cacs5RZP5RqE3ibmPxrstb+OfegNg=; b=AgZcMyul7eL+WfCjty2bENXy4HaBbAyUSxNaZ5MuNlihjlm2pJ9j3SwTxXtqXDAV7V y33mSof193DIBQ4iiz7bka/cJxf8FCJT4w04exeZQXGGSRnRtS7kzaNDLMY4Wz0fiNVf NJDQkunyzjTmbyfguoGbTqOQMy5+TfVH1dPE4HdPVt4c8PyNRGqB0HccXd6pcC2c9nDK 97BPikM86HE3hOVViCBNiQtj8xKcCgJjeosWSNfxLmEbkLcFonVnPJAnuOKo4a+jVQ6j krcupyk6GD4m3sQAmNy0QbalA5zVzV042iXY5iPjOjyQCb0ukpsxOwbnd4DrMMewGIm4 klRw==
MIME-Version: 1.0
X-Received: by 10.194.21.131 with SMTP id v3mr2869875wje.44.1382378276881; Mon, 21 Oct 2013 10:57:56 -0700 (PDT)
Received: by 10.227.202.194 with HTTP; Mon, 21 Oct 2013 10:57:56 -0700 (PDT)
In-Reply-To: <52656A0A.5010006@alvestrand.no>
References: <CAMvTgcfvaUMWJaD5zX2rt6DWOWBgHEA-SqNtOqxs_bOqw_Ygbg@mail.gmail.com> <CABkgnnXBdQOgs9OKYRrU4wYRghj3WH30=vo-q7iSVjUub1SKow@mail.gmail.com> <CABcZeBOGjsOTXPtAFh+KR9SDQv8tEtUDE3gLvSN+f5dZ2R2R1Q@mail.gmail.com> <CABkgnnVTv4jVZkCDHWKk_X8yb3VEGBLXh+sW00OCG6RXMNkpgA@mail.gmail.com> <5265386A.2020005@alvestrand.no> <CABkgnnUpwep1Gw+3t+bdc-vvatod-vQBpydSfcAqM93fk4vm+Q@mail.gmail.com> <52656A0A.5010006@alvestrand.no>
Date: Mon, 21 Oct 2013 10:57:56 -0700
Message-ID: <CABkgnnV+gV0kswygu_2_CpjdBv5PXU4Pv_FC0Hz-oyJ0Kn89DQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP fingerprint hash requirements
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 21 Oct 2013 17:58:17 -0000

On 21 October 2013 10:53, Harald Alvestrand <harald@alvestrand.no> wrote:
> you can't verify the certificate's signature,

That's somewhat orthogonal.  And thankfully, not necessary unless you
intend to use the certificate for anything more than its public key.
And in at least some of the cases we are talking about, we only need
that to work.

But then you are talking about a different sort of problem, which is a
well-known one, which is the validation of certificates.  I'm talking
about a=fingerprint.

v2.23.0 | Report a Bug | By Email