Delivery-Date: Thu, 31 Jul 2014 15:58:19 -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 486D11E0BA9;
	Thu, 31 Jul 2014 15:58:18 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6EDF530A84;
	Thu, 31 Jul 2014 19:58:15 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BC19C30A79
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:58:11 +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 UYa36UakJGIg for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 19:58:11 +0000 (UTC)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com
 [IPv6:2607:f8b0:4003:c06::231])
 (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 9C67A30A64
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:58:11 +0000 (UTC)
Received: by mail-oi0-f49.google.com with SMTP id u20so2114908oif.22
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 12:58:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:content-type;
 bh=+PIjDHZoGOwlTW6f6iO8V/MPMUW9KFcEXaJ/up3f0EA=;
 b=gYNtiUj8aj9qdNfbeWsv36Y9uNuSQn73UJCqlKZgd42xQmARXtHg+Kvvpy8xe4n64n
 l7YWrw1gZYMMgX6zagCc6fjzQJE+zVIObRX7Wp4y6het92RvwpB2sWwP5/lnNqpPVqN5
 UBpa4mF1MMq+gmgFgRODTd9Dgw3g5CO0UPap9SSzcxNfY8LVqMLZWQwXAe5IixYWJUng
 nxju7lP9wnhhplZSjCgho6mz3/g7NI4JLK63RZC+8Ppylh4owmcc/MfpboJGsFa1lf6W
 PKY5ONkAEpwrpnSTCX1DwHGtXvsmo0HArN2J6QxPlYdKFsORQd6M535JA4FNoIitorT2
 tZ9w==
MIME-Version: 1.0
X-Received: by 10.182.27.5 with SMTP id p5mr770347obg.42.1406836689226; Thu,
 31 Jul 2014 12:58:09 -0700 (PDT)
Received: by 10.202.224.84 with HTTP; Thu, 31 Jul 2014 12:58:09 -0700 (PDT)
In-Reply-To: <53DA96BA.8030200@bitmessage.ch>
References: <53D979A7.5050408@bitmessage.ch> <20140731000856.GA16023@nymity.ch>
 <53DA96BA.8030200@bitmessage.ch>
Date: Thu, 31 Jul 2014 12:58:09 -0700
X-Google-Sender-Auth: F7R-CMOjWvywevze_GnzQrNGOgQ
Message-ID: <CAJdkzEP0rdq5oUubQ+6iXdaA3LGs-pC5YPwW9Un7N6dFamGZSA@mail.gmail.com>
From: Damian Johnson <atagar@torproject.org>
To: Tor Mailing List <tor-talk@lists.torproject.org>
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>

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

We did this for a time...

https://trac.torproject.org/projects/tor/wiki/doc/badRelays

... but it was contentious so couldn't be continued. The topic of
transparency is an ongoing discussion but the compromise we made
between the camps for now is that this information will be in a
read-restricted git repository that all core tor contributors have
access to (previously it was so secret only three people or so had
access). For what it's worth both Philipp and I have been advocates
for greater transparency.
-- 
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

