Delivery-Date: Sat, 31 Jan 2015 17:23:58 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id EFBFA1E0BAE
	for <archiver@seul.org>; Sat, 31 Jan 2015 17:23:56 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 95B4B2E8F2;
	Sat, 31 Jan 2015 22:23:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 8589E2E80F
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 22:23:49 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id xlOE2fr_Ow5L for <tor-talk@lists.torproject.org>;
 Sat, 31 Jan 2015 22:23:49 +0000 (UTC)
Received: from smtp5.hushmail.com (smtp5.hushmail.com [65.39.178.142])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "Self-signed" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 4F85D2DA11
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 22:23:49 +0000 (UTC)
Received: from smtp5.hushmail.com (localhost [127.0.0.1])
 by smtp5.hushmail.com (Postfix) with SMTP id ED85B60224
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 22:23:45 +0000 (UTC)
Received: from smtp.hushmail.com (w3.hushmail.com [65.39.178.62])
 by smtp5.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 22:23:45 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id A336AC03CC; Sat, 31 Jan 2015 22:23:45 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 31 Jan 2015 17:23:45 -0500
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <4896dcf43cbf1e811dc789519b150192@openmailbox.org>
Message-Id: <20150131222345.A336AC03CC@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] WebRTC to uncover local IP
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


spencerone@openmailbox.org wrote:
>Understanding very little about WebRTC and STUN servers, what does
this 
>mean for people?

It means:
1) The network configuration of linux is more secure than the network 
configuration of windows. Even when using a VPN. Unless the VPN drops 
(and leaks).
2) If you're using a browser without some control over  how javascript
is used you'll encounter web bugs. Some of which might  make your VPN
service useless from the perspective of hiding your ISP  address.
3) For some reason Chrome is only able to succeed in using  UDP for
STUN. Meaning, if I understand correctly, that if you point a  Chrome
install to Tor via socks the STUN fails and doesn't leak. If  that's
any consolation...
4) Even if you restrict javascript use you  still need to worry about
the adversary who poisons your DNS cache. Such  an adversary can pose
as a whitelisted domain and force your ISP  address to leak.

So, the take home message:
1) Windows isn't a privacy oriented OS, and should be avoided if
possible. If you're not using windows you're already set.
2)  Irregardless of the OS you should be using extensions/addons to
control  how javascript gets used. Noscript/ScriptSafe for example. 
Alternatively disable the web bug using WebRTC Block (Chrome), or 
media.peerconnection.enable (FF). If you're using Tor Browser you're 
already set.
3) Consider using secure DNS methods (dnscrypt for  example) for your
non-torified browsers where you've opted to leave  webrtc enabled and
instead restrict the use of javascript.

-- leeroy
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

