IETF Logo Mail Archive

Re: [tram] Allow TURN to forward inbound connectivity checks without permission

Justin Uberti <juberti@google.com> Sun, 01 April 2018 22:09 UTC

Return-Path: <juberti@google.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 945B5126D73 for <tram@ietfa.amsl.com>; Sun, 1 Apr 2018 15:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 CB2yA0lhUG9v for <tram@ietfa.amsl.com>; Sun, 1 Apr 2018 15:09:54 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (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 4EC44120721 for <tram@ietf.org>; Sun, 1 Apr 2018 15:09:54 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id v134so7409613vkd.10 for <tram@ietf.org>; Sun, 01 Apr 2018 15:09:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qwijxSn1+CwEkoRYY5k/MHQ5whArzd1zKiOokQQJ3jQ=; b=VfZM+qxnqf/Qu8T42P7LOk8ezkA4xDAGjjVlFY8jsQ70q4SCK+t0xSUAPyeX3ePDV3 0dChYx1DTBTsLhEQ0vsOUo7NQyMMQYWqpc2Ye/092R4wG4BHm/rn7uOlCZTeYgCHF6zs nRUMHphD4grzef0OfS++dSLJY0aOskfxICZa0Dy5sC/Jv13PVIjZlaLeoaBFwtv21Rzp nZG3LtB0pvN10/LeGxiwGuOA2uOHs68ZOBW8UCPWGI6AZSFTn96CGTyfQC3rOP/5KiPm E2c1LCKiecTPIuw1GtIvpc5Qwgntf1m5xP161SyhGUAmTRgCcdQauPRYC0x+PnGLslbu h90w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qwijxSn1+CwEkoRYY5k/MHQ5whArzd1zKiOokQQJ3jQ=; b=ZrFKxazc48iQ0WKsakGNVD7n27Lp+XCB/u6gy4E3XIZeGB4ZcAs4C5uqwMCfRskcr1 P6X+yrKo4jKKpA7fjuofEIrkBh0oP4Eus8fXoh8YLb59WvD92l+KQ4mroW43bOlJayH4 6+2aY6SVSjsfMEqBM0PfxVIANNQr1zWYxAPnavmO6WhxrOGm0Z0SnZ8jeNaTKK79FlVq TB4fEWTuPAJLa2mr09IR0Xrar24bk2t68AUVNkBdtcuek2Zl6C2UESVvakPpM4xz0Yk5 Ak4QE4quuJgZY3t4vJlrqOWUhJ0cQZOAjht3FHC/KOjIZSOglzBxeyyR4qCKRtXZHuIe va+A==
X-Gm-Message-State: ALQs6tATyz4i61gmUg0wz8hRcLxJ1dl8kyUd/160hYSQ/+gXv6eKx9wj 5vLC0i5ZxexWmv8VnZ/Fm2QZfeZIvB3CijWuaL37ww==
X-Google-Smtp-Source: AIpwx49xNVOR3hlshtVk5NO5iO+QOuhg20+KfGCJBSfeDHSWZyHt1vlczn66JEq5Qyuo0R6QS/RsbzYMKvpd1Y/tzfU=
X-Received: by 10.31.157.216 with SMTP id g207mr3918362vke.111.1522620592821; Sun, 01 Apr 2018 15:09:52 -0700 (PDT)
MIME-Version: 1.0
References: <CANO7kWDd8NZ=svBONwzo6sE5YH3Y5MAdWFP2CQMiTg7M-b47AQ@mail.gmail.com> <c9ef837c-bf7c-decb-9542-8a9ddeda67fd@akamai.com> <E3AB81FC-D841-47A6-A0E2-775461779770@mozilla.com> <CANO7kWA4tmK7Di59tsjvCBoDdh-jW83FxMpqQH1-iSPGLS=mpA@mail.gmail.com> <8d57a9e5-5697-38f5-1b85-bf55930c6461@akamai.com> <BN6PR16MB142571E36A8B89196CB7B080EAAB0@BN6PR16MB1425.namprd16.prod.outlook.com> <CAOJ7v-1es3HqF4qN9Ha+v5jgGoONP0rs32vpKMJBP6j546uwqA@mail.gmail.com> <CANO7kWBS3GzjJxDt4oVhW2=Uqx8YFODY+HKEMZ+YH2cTvKa-5Q@mail.gmail.com>
In-Reply-To: <CANO7kWBS3GzjJxDt4oVhW2=Uqx8YFODY+HKEMZ+YH2cTvKa-5Q@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Sun, 01 Apr 2018 22:09:40 +0000
Message-ID: <CAOJ7v-1HHHTv+PuUTMFedK8XMoZCNvEtFfi0svChA_GBeFm+eQ@mail.gmail.com>
To: Simon Perreault <sperreault@jive.com>
Cc: TirumaleswarReddy_Konda@mcafee.com, Brandon Williams <brandon.williams@akamai.com>, Nils Ohlmeier <nohlmeier@mozilla.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Eric Rescorla <ekr@rtfm.com>, tram@ietf.org
Content-Type: multipart/alternative; boundary="001a1142763490b1840568d0bb5a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/nPFLrKs-7cwOEBXVUXoyiYUCHs0>
Subject: Re: [tram] Allow TURN to forward inbound connectivity checks without permission
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Apr 2018 22:09:56 -0000

On Sun, Apr 1, 2018 at 9:56 AM Simon Perreault <sperreault@jive.com> wrote:

> 2018-03-31 18:50 GMT-04:00 Justin Uberti <juberti@google.com>:
>
>> As Brandon says, the ufrag/pwd info could be posted along with the
>> address of the server, so while this raises the bar, it doesn't solve the
>> problem.
>>
>> I agree with Brandon that the only reasonable way to completely contain
>> this is some sort of server policy, e.g., some time window or session count
>> after which the permission bypass expires, meaning that someone running a
>> server would have to be continually requesting new allocations and posting
>> their address/credentials.
>>
>
> Do we need to completely contain this? Is there actually a problem with
> the proposal?
>
> Allowing STUN in allows someone to run a server if and only if the
> protocol masquerades as STUN. It doesn't allow a user to run an arbitrary
> server. For this to be exploitable, the user would also need to control the
> clients in some way.
>
> I can't think of a way this could be exploited practically. Maybe I lack
> imagination?
>

I don't think this is fatal to the proposal. I just think that we need to
be up front that this is a potential loophole, and have some explicit
discussion in the document of how one might solve this problem should it
become necessary (e.g., with server policy).

v2.23.0 | Report a Bug | By Email