Re: [rtcweb] [tram] TURN permissions for private ips

Simon Perreault <sperreault@jive.com> Wed, 05 August 2015 18:33 UTC

Return-Path: <sperreault@jive.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 287D01B3441 for <rtcweb@ietfa.amsl.com>; Wed, 5 Aug 2015 11:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 eqcJe6gU3qLD for <rtcweb@ietfa.amsl.com>; Wed, 5 Aug 2015 11:33:03 -0700 (PDT)
Received: from mail-oi0-f46.google.com (mail-oi0-f46.google.com [209.85.218.46]) (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 54E721B3442 for <rtcweb@ietf.org>; Wed, 5 Aug 2015 11:32:44 -0700 (PDT)
Received: by oio137 with SMTP id 137so23776456oio.0 for <rtcweb@ietf.org>; Wed, 05 Aug 2015 11:32:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FGLOFRbYUJFVEPMzJkGE1j04ATEC0umTkvsqKe+mBpk=; b=PMvSezXevWvuQDrKLzHQWs8z8uc9uKCjcIHTZvDLsFHFWSSXWiD2ywXonrM1zKa4uh z8z2zpCHtYKAqkv2WqetuTZ4U8VqEgMhWksmfQSTAa2qcSs4pWW2wRE4PjTQvTLouYke wZQv1CtBrGObKIK3rm9XNvcLkmG5RbCyjl6WZosN7X09wLzRjWkCl5K/Jf/x3i/lZbGw uHDzJJ1kjqxImHQUpO+w71lSYDwO2dQB59V/eI4mp/5lM28H6SEcNil37n7gPV594t9G HotYPVuXAIcUEhzYkWntErPay97Eft9SAH0Qej9RJKdl06fK8oI2nhU3CjDmdoeBLLPD BJ7A==
X-Gm-Message-State: ALoCoQkmd5c2ufeJPuRGa5HDusLQNCXppMGUhneaJbudz3pdRs85Hfd7/xnm298mx5+/hjj79Ffv
X-Received: by 10.202.71.6 with SMTP id u6mr9008045oia.36.1438799563755; Wed, 05 Aug 2015 11:32:43 -0700 (PDT)
Received: from Simons-MacBook-Air.local ([24.53.47.130]) by smtp.googlemail.com with ESMTPSA id l5sm2158006oey.5.2015.08.05.11.32.42 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Aug 2015 11:32:43 -0700 (PDT)
Message-ID: <55C256C8.80606@jive.com>
Date: Wed, 05 Aug 2015 14:32:40 -0400
From: Simon Perreault <sperreault@jive.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Philipp Hancke <fippo@goodadvice.pages.de>, rtcweb@ietf.org
References: <20150805130607.20844.70680.idtracker@ietfa.amsl.com> <CABcZeBMWVU9a1_e_47qddA04WhXG55QYzFA=dTrYgi+DuLQhKA@mail.gmail.com> <55C24293.5000603@cs.tcd.ie> <55C24C09.8020404@goodadvice.pages.de>
In-Reply-To: <55C24C09.8020404@goodadvice.pages.de>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/Jtf-7Y4LLJh_lBDC90Y3OWmKjes>
Cc: tram@ietf.org
Subject: Re: [rtcweb] [tram] TURN permissions for private ips
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: <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, 05 Aug 2015 18:33:04 -0000

Le 2015-08-05 13:46, Philipp Hancke a écrit :
> If a peer sends candidates with IP addresses from the private space,
> permissions for those are created at the TURN server. Potentially not
> utilising transport encryption even.
> 
> I doubt those candidates ever work, so from a privacy point of view it
> seems that clients should not create those permissions in the first
> place. And ICE should probably not try to create pairs.

It's not up to the client to determine what addresses might not might
not work for a given TURN server. There are lots of weird NAT
configurations out there that play games with RFC1918 addresses and can
easily trick clients into doing the wrong thing.

Instead, the server should be the one doing that check because it only
has access to reliable information. It should use the existing mechanism
and return 403 Forbidden for addresses it doesn't like. See RFC 5766
section "9.2. Receiving a CreatePermission Request":

   The server MAY impose restrictions on the IP address allowed in the
   XOR-PEER-ADDRESS attribute -- if a value is not allowed, the server
   rejects the request with a 403 (Forbidden) error.

Simon