Delivery-Date: Tue, 24 Jun 2014 15:12:00 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 E139F1E0EBE
	for <archiver@seul.org>; Tue, 24 Jun 2014 15:11:58 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7B4982F5BA;
	Tue, 24 Jun 2014 19:11:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B7FB82F789
 for <tor-talk@lists.torproject.org>; Tue, 24 Jun 2014 19:09:00 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 OoYGRr5SC8OX for <tor-talk@lists.torproject.org>;
 Tue, 24 Jun 2014 19:09:00 +0000 (UTC)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com
 [IPv6:2607:f8b0:400c:c01::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 961EB2F780
 for <tor-talk@lists.torproject.org>; Tue, 24 Jun 2014 19:09:00 +0000 (UTC)
Received: by mail-ve0-f173.google.com with SMTP id db11so844670veb.18
 for <tor-talk@lists.torproject.org>; Tue, 24 Jun 2014 12:08:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=LIadYc27G4A7VKtZZ9aA3xg5M8HtClKgJ1FEaKXqfqQ=;
 b=UqEtuOagF7IaW9yMeG39grVT2fjjv3ngHh9HZ9Zf7j2Tt5kg910oe45zmqUJVSsc0+
 O7Ia2vTZajsPvF5fgQMvkZdtP1XNErG9LX4SEBJ/Bn/cH3Zg2Jvbg1x2XVQvjvZjPmfv
 ZZbfVQ1VDpYRMtHWSA2SCI4d+fYOEYFCqxwzzZENyEIjKWeKovXadhkJLpW8RMCRfXop
 Ec3OcR3ZceMWTpmdvfuL0PFprtbZoK73Z8rxldKLyRbgvIRm6xBP9qMJHXHtZh1I9Leq
 OagIu7Uf2IIUbz3fmqqxoQFjQQc69bl0smEIrs3Q8rfZW6NSQCe0O419MAAIpCD8lGiO
 0FGw==
MIME-Version: 1.0
X-Received: by 10.220.122.132 with SMTP id l4mr2271943vcr.41.1403636937923;
 Tue, 24 Jun 2014 12:08:57 -0700 (PDT)
Received: by 10.221.65.198 with HTTP; Tue, 24 Jun 2014 12:08:57 -0700 (PDT)
In-Reply-To: <CAKkunMZZ752LeEJDPcZHavtaOwMXHewJksTmKjLqoPC_8fdtaQ@mail.gmail.com>
References: <CAKkunMZZ752LeEJDPcZHavtaOwMXHewJksTmKjLqoPC_8fdtaQ@mail.gmail.com>
Date: Tue, 24 Jun 2014 15:08:57 -0400
Message-ID: <CAD2Ti2-v3ZPUi7gZ8hkqu5f02uj1_uXe-h+aAAZBYzSM9H1CYg@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Running an exit node which exits on a different IP
 than it listens to
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>

On Tue, Jun 24, 2014 at 9:07 AM, Anders Andersson <pipatron@gmail.com> wrote:
> exit traffic out on an IP that's different from what was advertised.
>
> However, this made me think that it is perhaps not such a bad idea if
> more exit relays did that, even slower ones. I have access to a couple
> of IP numbers that I could easily configure in this way.
>
> Basically: Use one IP for Tor traffic, and one IP for exit traffic.
> The Tor traffic IP:Port is what would be advertised to the Tor
> network, and only that.
>
> The reason would be to minimize the chances of the exit IP ending up
> in some overzealous blacklist. I'm pretty sure that a lot of the
> blacklist operators just scrape the public list of relays and then
> they end up in a lot of places where the customer is not even aware
> what is being blocked. This is painfully obvious to people running a
> non-exit relay from home, when trying to use IRC or other services.
>
> Is this a good idea to do if you have the resources? Will it cause any
> non-obvious problems? I guess one problem is that check.torproject.org
> will show that you're not using Tor

So what? What's more important to you, helping users get around stupid
consensus scraping RBL blocks and censors, or having check.tpo look pretty?
Tell users to retest after 'new identity' or to test tpo's onion
instead, because:
 "Congratulations. This browser is configured to use Tor."
And learn a little more before they go installing stuff by default and stumbling
about the net assuming all is safe because some little widget told them so.


This has recently been discussed, feel free to implement either model...

https://lists.torproject.org/pipermail/tor-relays/2014-May/004516.html
...
https://lists.torproject.org/pipermail/tor-relays/2014-June/004691.html
https://lists.torproject.org/pipermail/tor-relays/2014-June/004693.html
-- 
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

