Delivery-Date: Thu, 31 Jul 2014 15:19:45 -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_SIGNED,
	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 EE90E1E0BC2;
	Thu, 31 Jul 2014 15:19:43 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9949330A1C;
	Thu, 31 Jul 2014 19:19:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B995330A17
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:19:37 +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 D9HH2TrgCtA5 for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 19:19:37 +0000 (UTC)
Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252])
 by eugeni.torproject.org (Postfix) with SMTP id 5658630A10
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:19:37 +0000 (UTC)
dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail;
 c=relaxed/relaxed; q=dns/txt;
 h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References;
 bh=tX2qS873urxK6OA7ueBnscdwjVpe75JKui5Z/BautP8=;
 b=qkcR6jyuqcU6k7WXJg9vlZiUxjrXnpuNaLW15ON58K75yGZjKOiW749FohTZ8qZljy2Y4QZWTWJ4S3evJzXUFKozIXRSQUe5ofe8z3Q4GPD597bdMN4iYzkn+YumQF7OqwBZGkVdmpoFa+V+ocq5yNyoqA+FsKwV/Z/FvPXoOqk=
Received: from 127.0.0.1 (BITMESSAGE [127.0.0.1]) by mail.bitmessage.ch
 ; Thu, 31 Jul 2014 21:18:39 +0200
Message-ID: <53DA96BA.8030200@bitmessage.ch>
Date: Thu, 31 Jul 2014 19:19:22 +0000
From: Nusenu <BM-2D8wMEVgGVY76je1WXNPfo8SrpZt5yGHES@bitmessage.ch>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53D979A7.5050408@bitmessage.ch> <20140731000856.GA16023@nymity.ch>
In-Reply-To: <20140731000856.GA16023@nymity.ch>
Subject: Re: [tor-talk] 'How to report bad relays' (blog entry)
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> I believe that the mere fact that a relay was blocked (via BadExit
> or reject) can be published.

Will dir auth ops make the list of rejected relays including its
reason for removal available to the public for transparency?

>> where can we find a list of all relays that have been removed
>> from the consensus in the past so far? I tried to find 'rejected'
>> flagged relays on the following page but wasn't successful. 
>> https://consensus-health.torproject.org/
> 
> Rejected relays are not part of the consensus

If I understand option AuthDirReject correctlty, a dir auth. is not
voting for such a relay with the 'rejected' flag*, it is simply not
putting that relay in its vote at all.

So there is currently no way to determine whether a relay has been
"disappeared" by dir auth ops or the relay op decided to discontinue
running the relay itself?

(I was not looking for BadExit relays - they are easy to spot in the
consensus.)

*) actually there is no such thing as a 'rejected' flag
https://gitweb.torproject.org/torspec.git/blob/HEAD:/dir-spec.txt#l1604
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJT2pa6AAoJEDcK3SCCSvoeCS4P/RkGScRHL6E3sTjHAxCnorbE
rBD/lbyXEQf5g5y4B/eTuVob/qzT2BvgKPdimig1hBy0s0OR0CdFon+LsXKr18IK
PRzmZn4+i8xlQIWwq6ZEBqNLBruI3+LzVOCgf4T99V89OnKCmJyqNchZkiChXR1Q
T9zXNsrieJlND1DB3XwQ9IzYKdKyb0MREn+n7qkwcZqf28LLrLULUQ1kEHU2KqzK
AvA30vsgiLiyCelMTcHu1nMDanw3rCa0NhOFEcfYCiKuuWoyYz4kPkRJ5nFkeBfC
i4EVO3zqijN/En+Fn14+Yu2b80lqWgcxQjbH3uphwrbeG8BmJMaqnp0xR2kravQf
38zC/JJuUk7B/yBGtbpuqg9H/6DmcOluRIL/BbNwpQJgMF5VQA99i9eYXwwDtWT6
nhIgUwO918UClKtF9p05PGgmzQ8nILHCRioynklE8eQlmd/vwIYd4rj4NjNOTbXD
Q3OPADlHO4vwHLFPAuK75NGnMI48GdE3Ne25P26jpymd13TpWfWEEATEbikrjq05
I3ArDR3t8MX5WzD+HLt5EkRHXQvSMumQaNeZaeOkZR85K2wJTjJlsG7iLo9THVky
iinAxiSh0qcWCs31Gtmnw6C7Gv9KLL1VB5t+s0KFj4fcgUyNwwDafqL3HH5B3AXQ
abJUrVDpRfrvIZUXULXS
=n2Pt
-----END PGP SIGNATURE-----

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

