Delivery-Date: Mon, 12 Oct 2015 21:43:58 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 327C91E0BF1;
	Mon, 12 Oct 2015 21:43:56 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3391837FDC;
	Tue, 13 Oct 2015 01:43:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D576137FC7
 for <tor-talk@lists.torproject.org>; Tue, 13 Oct 2015 01:43:45 +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 hVLxHNfGkxaN for <tor-talk@lists.torproject.org>;
 Tue, 13 Oct 2015 01:43:45 +0000 (UTC)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com
 [IPv6:2a00:1450:4010:c04::22c])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 6E45937F64
 for <tor-talk@lists.torproject.org>; Tue, 13 Oct 2015 01:43:45 +0000 (UTC)
Received: by lbcao8 with SMTP id ao8so3113023lbc.3
 for <tor-talk@lists.torproject.org>; Mon, 12 Oct 2015 18:43:42 -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=6QRQ05BvcnvYypshJ8Cdkwd518n9r+t1rjWFSQAefeA=;
 b=wonDG7UCX7e85DQzsMV2C7xPahr696I4FroavPF6uqCtW9mcibwbgoCXNyzM7BtQUD
 RYke9i3FDGV9SIfCDwAt2ksxbMdD8NnxnAkydzemE35o0+ZOozw7+w59RfKymeGDwg7V
 RczLnd51DKnS5VwwO5oapF3GXGc7UB6t4iec/NaOwOzpfPH+W4+14iNccLRG0kXXMyYv
 GbZig0IKKdQkqFgljoP/whbOG9hEr2/0QX32VI5BHseTanJ25lMqYizA7VqPcfcEdVmT
 7yuk10e4116F4j+da66swWyHRR/UKfOQI511wchO6qkIP8cQWzQqYuhSrxsL51i5etMk
 VynA==
MIME-Version: 1.0
X-Received: by 10.112.170.70 with SMTP id ak6mr10326206lbc.107.1444700622388; 
 Mon, 12 Oct 2015 18:43:42 -0700 (PDT)
Received: by 10.25.145.142 with HTTP; Mon, 12 Oct 2015 18:43:41 -0700 (PDT)
In-Reply-To: <20151013012057.GD2119@localhost.localdomain>
References: <6.2.5.6.2.20151011115307.0711bbc0@binnacle.cx>
 <CAD2Ti2-KsGjF5F9REyh2WHJtDfuC+dQoqa4n4fY05wfy0sXv+A@mail.gmail.com>
 <20151013012057.GD2119@localhost.localdomain>
Date: Mon, 12 Oct 2015 18:43:41 -0700
Message-ID: <CAJVRA1RgMVQX9i8PSQ7BW5z3SHhx3z3RSfcTvxUYPvO5W1y82w@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org, sh-expires-12-2015@quantentunnel.de
Subject: Re: [tor-talk] Mulihomed flag for nodes (from Re: why are some exit
 IPs missing from Exit IP DB?)
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 10/12/15, sh-expires-12-2015@quantentunnel.de
<sh-expires-12-2015@quantentunnel.de> wrote:
> ...
> Tor users aren't entitled to special treatment,

at times it is desirable to avoid the usual "knee-jerk" responses, however.

there is a trick, which is to monitor the consensus. any new relay
identity, or new IP associated with an existing entity.

on event of a new relay or IP, attempt an exit check.

if the exit is not currently in the listed DNSRBL, use it as quickly
as possible as "new-not-yet-blacklisted"

note that there are plenty already using this technique, and you must
race the horde, depending. (the people reading this in some search
engine cache surely spammers looking to maximize their abuse of the
Tor network. ;)



>> the great side effect that such exits are usable to
>> circumvent similar braindead / hating censorship
>> directed at tor users.
>
> Have you ever considered, that people who
> operate hidden services for websites, like to redirect
> people to said hidden services instead of relying
> on exits?

you may like my theory of the whole world going hidden service, soon
enough. since the public internet is all DEF CON wireless, whether you
admit it to yourself or not. *grin*



> Sorry, if that sounds scary, but some relay operators
> I met the this year hat quite a negative relay experience.

i'd like you to tell us more about these negative relay experiences.

i don't doubt them. but i find your misguided understanding of and
pre-occupation with only Tor's detriments interesting.




> I am currently wrapping my head around this, trying
> to figure out if it makes correlation attacks easier
> or MITMing and inserting convert channels between
> arbitrary nodes harder.

this quantified risk analysis at your disposal sounds quite useful.
looking forward to details!



> While we are at it, I consider having the exit ip for
> multihomed nodes in the consensus beneficary. If
> you like to start including additional information into
> the consensus consider the AS too.

you don't understand why this isn't practical. but that's ok.

totally different from AS for OR endpoint.



> The data is available form the RIRs, I am using it with
> a Tor monitor, that isn't libre and I am not sure how the
> RIRs would like to have their services put under load.

you're a considerate and careful Internet citizen, thank you!



> Anyway, I am moving this to tor-talk with the intention
> to discuss, at least, a multihomed flag.

multi-homed flag must die in a fire. don't even consider it!


best regards,
-- 
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

