IETF Logo Mail Archive

Re: [rtcweb] Please require user consent for data channels

Iñaki Baz Castillo <ibc@aliax.net> Sat, 18 July 2015 09:32 UTC

Return-Path: <ibc@aliax.net>
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 6E83D1B29E2 for <rtcweb@ietfa.amsl.com>; Sat, 18 Jul 2015 02:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.678
X-Spam-Level:
X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
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 w9e_zzTt8Pzm for <rtcweb@ietfa.amsl.com>; Sat, 18 Jul 2015 02:32:04 -0700 (PDT)
Received: from mail-yk0-f177.google.com (mail-yk0-f177.google.com [209.85.160.177]) (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 423DD1B29DF for <rtcweb@ietf.org>; Sat, 18 Jul 2015 02:32:04 -0700 (PDT)
Received: by ykax123 with SMTP id x123so107345379yka.1 for <rtcweb@ietf.org>; Sat, 18 Jul 2015 02:32:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=15bsETs5L+aih3P12qgtmxNPRv/qwS4g8TYDnrzVylg=; b=UKjaoesldh2eOIkHQBNFMZMbb5/cNG0FF/QHjCW8WWqKYJZDB9L/Bd1k58LE8phGrK 4H3uXB0UKYXwdpk6TNxWn75oTAyMpstvdpJbH1c4Z5noa1zSk5CWm4aDxYjsXGWLuX0b Fqh8jApXTB5sQNnoVzCmoR8lcI5XnGX9oP1QutTnl+D07JwpBSNn6QKM4lboaKu39fF2 4iMhXkOGKzAxJQ+5bNaFKHhzmoZd8bz/yzse+t2ZbyXw/w4sLZlefL4YCrHb67arQxw+ hU6tUSYobRg0f5KzTc3qfUelilX2b4gst5xgGHX+Hgv4oRfkg6f3WenTfxIOFAdok/Qy quxQ==
X-Gm-Message-State: ALoCoQl/BSBTgR283sJAS4Ym5mMsyGmIYiSFYcbtOwyJuXE2sWo/F9OehE21mtUq+g7FjIgyogew
X-Received: by 10.129.77.213 with SMTP id a204mr19898915ywb.40.1437211923681; Sat, 18 Jul 2015 02:32:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.215.206 with HTTP; Sat, 18 Jul 2015 02:31:44 -0700 (PDT)
In-Reply-To: <CAOJ7v-1cB47793yH+-mWrdU9rNqX=+HadZpbRf3PezXspqLm1A@mail.gmail.com>
References: <CA+65OspMD_PVjk0BXh7t4LtjmFDcDatoeNjFQOO_OVtC-Br+OA@mail.gmail.com> <CAOJ7v-0UBGtP0-atxP7X4OTj-H6Lost5o42aAS65mA6CEqcQsw@mail.gmail.com> <CA+65OsrhXHK+cRAFLCZFt+34vr8eRhj+CN3DgznUBfSwmWYggw@mail.gmail.com> <CAOJ7v-24VCW6kkn7LOLkqZzhYEU0r=nmd_F7Zns1rnyqKN6xAg@mail.gmail.com> <55A95364.2070806@gmail.com> <CAOJ7v-3t9BQabR2e4EHs4G0Sec4sU9DFC2aiSXXYrat+an+RYg@mail.gmail.com> <55A96DA3.1040907@gmail.com> <CAOJ7v-1ui7349NzK6NZNRHPbnHWZajctk4cDgMKqRZSv47EYdA@mail.gmail.com> <55A9860D.8030903@gmail.com> <CAOJ7v-3LGd32rnpFVW_U0s3+iVaJXsL4vt_YAo=cyp6YyOArdw@mail.gmail.com> <55A99148.1040105@gmail.com> <CAOJ7v-1cB47793yH+-mWrdU9rNqX=+HadZpbRf3PezXspqLm1A@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Sat, 18 Jul 2015 11:31:44 +0200
Message-ID: <CALiegfkmk0MqBwEQq3RoFOGRK=9VXh24b_R8zE2spOCQigK=zQ@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/C4CYhtWdzo48jXd-FvQblQrvbLU>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Please require user consent for data channels
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: Sat, 18 Jul 2015 09:32:05 -0000

2015-07-18 2:19 GMT+02:00 Justin Uberti <juberti@google.com>:
> Typically with a VPN, the non-VPN interface is locked down so it only has a
> single route: to the VPN server. However, split tunnel VPNs allow the
> non-VPN interface to route to other addresses (possibly, for performance
> reasons), so in this case, the non-VPN-host-candidate STUN request will be
> sent successfully from the non-VPN interface.

Is that really the most common VNC scenario? Never seen that. I
thought that usually the VNC client adds its own network routes to
reach other users/servers within the same VNC network and leaves the
default route (and others) intact.

My worries are about ICE gathering and the timeout it causes when a
STUN request is sent to the STUN/TURN server from all the local
interfaces. Security/privacy issues (if we consider that leaking all
the host and reflexive addresses is an issue) can happen during ICE
gathering and also when connecting the remote peer.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email