IETF Logo Mail Archive

Re: [rtcweb] Alexey Melnikov's Discuss on draft-ietf-rtcweb-security-arch-18: (with DISCUSS)

Adam Roach <adam@nostrum.com> Wed, 06 March 2019 19:37 UTC

Return-Path: <adam@nostrum.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 3C10F128B36; Wed, 6 Mar 2019 11:37:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 PWiZD556ThHe; Wed, 6 Mar 2019 11:37:28 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 1AE2F1275F3; Wed, 6 Mar 2019 11:37:28 -0800 (PST)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x26JbJi1080570 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 6 Mar 2019 13:37:20 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1551901041; bh=AxflgBu55NZAtnOTwVP8RPUuYWxLW7POz9nE2yvGETE=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=QVTCDSTBG7AFmaWqXkw7bjopoo6n6ETLjAg43B/mxpU5+YsJlcjRlhVCTIlJnMlbs 21K+1JWuUkbgJVhu1i6M5mHH1rvAmSCK6d6ddpLWUfOiR60lZ86eK1lbIwmI72m/71 HrR2+MGQGLPvjYSy5Fv2r7Fz/VZnybhvh9TCRpCc=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
Cc: rtcweb-chairs@ietf.org, rtcweb@ietf.org, sean@sn3rd.com, draft-ietf-rtcweb-security-arch@ietf.org
References: <155177956812.24656.14146723462005957233.idtracker@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <2c600fc6-ca2c-2cd5-f677-6edcd0a6f3b7@nostrum.com>
Date: Wed, 06 Mar 2019 13:37:14 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.5.2
MIME-Version: 1.0
In-Reply-To: <155177956812.24656.14146723462005957233.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/ciZa8-_Qm6uXpS4EHtf5tb6sqss>
Subject: Re: [rtcweb] Alexey Melnikov's Discuss on draft-ietf-rtcweb-security-arch-18: (with DISCUSS)
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, 06 Mar 2019 19:37:30 -0000

On 3/5/19 3:52 AM, Alexey Melnikov wrote:
> My apologies for filing a procedural DISCUSS on this, but I am looking at:
>
> 7.5.  Determining the IdP URI
>
>     3.  The path, starting with "/.well-known/idp-proxy/" and appended
>         with the IdP protocol.  Note that the separator characters '/'
>         (%2F) and '\' (%5C) MUST NOT be permitted in the protocol field,
>         lest an attacker be able to direct requests outside of the
>         controlled "/.well-known/" prefix.  Query and fragment values MAY
>         be used by including '?' or '#' characters.
>
> "idp-proxy" is not registered in the IANA's
> <https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml>
> registry and this document doesn't register it either. If I missed where this
> is registered, please point me to the right document. If I haven't, please
> register it in this document.
>

Good catch! Thanks.

/a

v2.23.0 | Report a Bug | By Email