Delivery-Date: Thu, 02 Jul 2015 17:53:17 -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 100621E0A30;
	Thu,  2 Jul 2015 17:53:16 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A3FCB34E1E;
	Thu,  2 Jul 2015 21:53:09 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 757CA34E10
 for <tor-talk@lists.torproject.org>; Thu,  2 Jul 2015 21:53:06 +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 0RVS4n5Habk9 for <tor-talk@lists.torproject.org>;
 Thu,  2 Jul 2015 21:53:06 +0000 (UTC)
Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.200])
 (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 4966134E0D
 for <tor-talk@lists.torproject.org>; Thu,  2 Jul 2015 21:53:06 +0000 (UTC)
Received: from smtp3.hushmail.com (localhost [127.0.0.1])
 by smtp3.hushmail.com (Postfix) with SMTP id F2A79E015D
 for <tor-talk@lists.torproject.org>; Thu,  2 Jul 2015 21:53:02 +0000 (UTC)
Received: from smtp.hushmail.com (w6.hushmail.com [65.39.178.92])
 by smtp3.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Thu,  2 Jul 2015 21:53:02 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id D61FA2387B; Thu,  2 Jul 2015 21:53:02 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 02 Jul 2015 17:53:02 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <55959D87.9010104@openmailbox.org>
Message-Id: <20150702215302.D61FA2387B@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Doctor's possible sybil attack report from
	2015-07-02 - 'cloudvps' (XL Internet Services)
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>

Hi nusenu,

I'm glad you asked. Why don't they have the exit flag? It probably has
something to do with MinMeasuredBWsForAuthToIgnoreAdvertised being 500
by default. If you look at consensus-health [0] you see much more than
500. This means, and I'm only quoting the spec [1], that these relay
need measured bandwidth to have a weight assigned to them. In the
absence of a consensus weight (note they're all zero), these relay
have 0 probability of being chosen. So they need to respond to a
bandwidth scan, and they haven't.

[0] https://consensus-health.torproject.org/#bwauthstatus
[1] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1895

Is it any consolation that the running relay are, by default, in two
family? 85.222.0.0/16, and 213.187.0.0/16 form a family by default in
tor (unless EnforceDistinctSubnets is 0).

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

