Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling

Philipp Hancke <fippo@goodadvice.pages.de> Tue, 03 April 2018 13:17 UTC

Return-Path: <fippo@goodadvice.pages.de>
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 E6FB012778D for <rtcweb@ietfa.amsl.com>; Tue, 3 Apr 2018 06:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ZaiWelg1pSSO for <rtcweb@ietfa.amsl.com>; Tue, 3 Apr 2018 06:17:36 -0700 (PDT)
Received: from lo.psyced.org (lost.in.psyced.org [188.40.42.221]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AB9E12025C for <rtcweb@ietf.org>; Tue, 3 Apr 2018 06:17:36 -0700 (PDT)
Received: from [192.168.1.230] ([84.20.98.117]) (authenticated bits=0) by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id w33DHd5L011295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <rtcweb@ietf.org>; Tue, 3 Apr 2018 15:17:41 +0200
To: rtcweb@ietf.org
References: <1D5B431C-801E-4F8C-8026-6BCBB72FF478@sn3rd.com> <e6938f7d-542d-736b-0a3d-9269d7dd06e5@cs.tcd.ie> <CAOW+2dv1ORz2tEkgDTvdM1DtgyOdgXqKU30T4QhLAp1NT+rirg@mail.gmail.com> <CAOJ7v-0tCcg3FdzyfSJ6Y3JaH-TivFf-Sey6+tD8BANJKsjqtQ@mail.gmail.com> <1fceb3c4-35f3-34f7-de1d-79d5805e6d22@gmail.com> <9517D601-D3E8-46E1-94E5-7EC29FD6319B@sn3rd.com> <b5d323ac-2205-2aee-05c9-f270e80215f5@gmail.com> <CAOJ7v-0+hr-NddbLCwgjkfyEFEzoLYW8BcE5OYZ+HUiqDRnarg@mail.gmail.com> <0dee004d-159a-a9be-a0b8-ecbfd4204d72@gmail.com> <03D3C806-B93F-4CD0-B57B-507B07E869A0@westhawk.co.uk> <540AF425-A798-41BB-8C22-9F697DF46117@westhawk.co.uk> <562af54d-9fcd-48c3-5709-6c8fa469e995@cs.tcd.ie> <8D1E1BA7-9BDE-4302-A698-B1C3E4686F12@westhawk.co.uk> <8d528cc5-84d9-c0cf-be5a-19e836f7ca89@cs.tcd.ie> <CABcZeBPXZ54xf-H8wCrmEF1_2F43OXRaoiHNsobmEgGtLiC+6A@mail.gmail.com> <443FC3E5-891C-49BB-90A1-C3139D3C0655@iii.ca> <B39901B1-6DB1-4856-A6D8-BEF945766361@westhawk.co.uk>
From: Philipp Hancke <fippo@goodadvice.pages.de>
Message-ID: <a94ec743-96df-99a4-7e93-615c20bf722c@goodadvice.pages.de>
Date: Tue, 03 Apr 2018 15:17:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <B39901B1-6DB1-4856-A6D8-BEF945766361@westhawk.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/XvkE5glKCjd9Dcw2KluhHU5Pazw>
Subject: Re: [rtcweb] WGLC for draft-ietf-rtcweb-ip-handling
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 03 Apr 2018 13:17:40 -0000

Am 03.04.2018 um 11:14 schrieb T H Panton:
> In case anyone thinks this issue will go away if we ignore it:
> 
> https://www.theregister.co.uk/2018/03/29/almost_a_quarter_of_vpns_tested_leak_ip_addresses/ <https://www.theregister.co.uk/2018/03/29/almost_a_quarter_of_vpns_tested_leak_ip_addresses/>

It turned out the issue in this case is
a) browser extensions that add a proxy server calling themselves a "VPN"
b) said browser extensions being unaware of the Chrome Extension API to 
set mode 4 which prevents UDP from being used if a proxy server is set.

See https://voidsec.com/vpn-leak/ for the original article. Its 
interesting research and shows that the actual problem is not VPNs in 
split mode as I had assumed.