IETF Logo Mail Archive

Re: [rtcweb] Benjamin Kaduk's Discuss on draft-ietf-rtcweb-security-arch-18: (with DISCUSS and COMMENT)

Sean Turner <sean@sn3rd.com> Wed, 15 May 2019 14:20 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 3ED3E12013E for <rtcweb@ietfa.amsl.com>; Wed, 15 May 2019 07:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable 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 NF9v-Zj56V5N for <rtcweb@ietfa.amsl.com>; Wed, 15 May 2019 07:20:29 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 6C9B51200F5 for <rtcweb@ietf.org>; Wed, 15 May 2019 07:20:27 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id h1so3486369qtp.1 for <rtcweb@ietf.org>; Wed, 15 May 2019 07:20: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:cc :content-transfer-encoding:message-id:references:to; bh=9zgLVFtR96GktN/PiLd7ArORnSPI0MQFWmkAv+pw2zk=; b=f59ufJuNJcy4z/9Iobczx3GRefOdWGynnn9I/Wi9lCVQYK0qY4Omn7xfrO5z6Kqx3V jmkMmrPETGWm9PfAWXcJmgx0dcmvErA4z80gpP6P0WCV2HNF5J0UJPAe+RxpOmxkEP+P h26R1VQ7aVbWm/Z/2IVggRiRvdYx2r7UEeZCQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9zgLVFtR96GktN/PiLd7ArORnSPI0MQFWmkAv+pw2zk=; b=WUHfVNQTF9qKAtzemESUadtLMLIdmtF7NDGiQKUySYjVV4lowb5TGzZKVDcCYC+1eB bkUe0UwCOKVg4uO7Mimw0+qR97irIENZffepDQJM+r2/akjZEcc/0uQ69Ib4G4baHNEi LoCDymrTODhofqr8JIOdQF+bd8b3sJ8F8z5268/WmsMO7vQSBfZYzWVKOEGLaUBwGQLN BfcTyYwqmGmObha76/glT99+kQE0rvScXF8cQA0DtFM0XtudtJ65m0b9Dc2uvwzcQO13 d+ZsePgy/zdwWDtr8t/ftaJbN5HFJl+kbEkzRg9WssGZyTvykMI8U0y+a0ovrxnjMz7N U9uw==
X-Gm-Message-State: APjAAAWlP/U9knBT57RSO1t9bPY8l4le48v0R76eW8Sa+2UWelalBbRN ggT58pkU6+uwGRoQXNe/Rfv/sQ==
X-Google-Smtp-Source: APXvYqzxqpxLHqEkzEnv9QoMw3SHRzaz6CzfyCSuamgUcrmfA0UEJbLhyn9MEVZBSyUUMehEbto1vA==
X-Received: by 2002:ac8:66d6:: with SMTP id m22mr35206600qtp.323.1557930026544; Wed, 15 May 2019 07:20:26 -0700 (PDT)
Received: from sn3rd.lan ([75.102.131.36]) by smtp.gmail.com with ESMTPSA id a64sm1029884qkd.73.2019.05.15.07.20.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 May 2019 07:20:25 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <746BFA74-9B05-4754-B610-ED24BF0EC049@sn3rd.com>
Date: Wed, 15 May 2019 10:20:24 -0400
Cc: draft-ietf-rtcweb-security-arch@ietf.org, rtcweb-chairs@ietf.org, RTCWeb IETF <rtcweb@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1043BBB7-059A-4A83-92DD-926BB2AAD22D@sn3rd.com>
References: <155192582265.13773.4546017380973569678.idtracker@ietfa.amsl.com> <746BFA74-9B05-4754-B610-ED24BF0EC049@sn3rd.com>
To: The IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/kAzV-gZsMjPsW3Ku8W_zDpXZ6Pk>
Subject: Re: [rtcweb] Benjamin Kaduk's Discuss on draft-ietf-rtcweb-security-arch-18: (with DISCUSS and COMMENT)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 15 May 2019 14:20:30 -0000


> On Apr 14, 2019, at 13:02, Sean Turner <sean@sn3rd.com> wrote:
> 
>> I'm a bit unclear about how the port in the IdP URI's Authority (Section
>> 7.5) would get discovered.  If it can be remotely supplied, there may be
>> risks in just trusting blindly whatever value is received.
> 
> Ted started a thread on this here:
> https://mailarchive.ietf.org/arch/msg/rtcweb/8dtCkSeXWUsb_y2SRyFlbQ5r93w
> We’ll see where it lands.

Submitted a PR to address this:
https://github.com/rtcweb-wg/security-arch/pull/92

spt

v2.23.0 | Report a Bug | By Email