Delivery-Date: Tue, 26 May 2015 18:45:27 -0400
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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,T_RP_MATCHES_RCVD 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 6C0291E13DE;
	Tue, 26 May 2015 18:45:25 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 27B0C35061;
	Tue, 26 May 2015 22:45:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9748E35020
 for <tor-talk@lists.torproject.org>; Tue, 26 May 2015 22:45:17 +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 IY2DM6W5D5b3 for <tor-talk@lists.torproject.org>;
 Tue, 26 May 2015 22:45:17 +0000 (UTC)
Received: from smtp10.hushmail.com (smtp10.hushmail.com [65.39.178.143])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "smtp.hushmail.com" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 6A5FB34EDC
 for <tor-talk@lists.torproject.org>; Tue, 26 May 2015 22:45:17 +0000 (UTC)
Received: from smtp10.hushmail.com (localhost [127.0.0.1])
 by smtp10.hushmail.com (Postfix) with SMTP id B1F7CC01E9
 for <tor-talk@lists.torproject.org>; Tue, 26 May 2015 22:45:14 +0000 (UTC)
Received: from smtp.hushmail.com (w2.hushmail.com [65.39.178.46])
 by smtp10.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Tue, 26 May 2015 22:45:14 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id A7701E0488; Tue, 26 May 2015 22:45:14 +0000 (UTC)
MIME-Version: 1.0
Date: Tue, 26 May 2015 18:45:14 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <20150526224003.56E45E0488@smtp.hushmail.com>
Message-Id: <20150526224514.A7701E0488@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] SOCKS proxy to sit between user and Tor?
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>

Of course turning off remote resolves to use a local resolver (free of
conflicts) also has this downside. Settings persist between tbb launch
so if remote DNS is turned off and a local resolver is down a leak
occurs using the system DNS.

If anything, for the sake of your sanity try to keep everything in the
plugin.

On 5/26/2015 at 6:40 PM, "l.m"  wrote:I'd like to point out that if
you decide to use another SOCKS proxy
you may encounter another problem. Suppose I bypass the port assigned
to your custom proxy and instead point to the usual tor proxy. This
might occur if a user manually configures the proxy and cannot tell
the difference between the two. Most likely it'll fail and they'll
notice. In a worst case, your blockchain resolves are bypassed and a
leak occurs. 

It also raises the question of whether you really want to have a SOCKS
proxy for both regular firefox and tbb/tor.

--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
-- 
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

