Delivery-Date: Wed, 17 Feb 2016 20:07:54 -0500
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_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	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 98E271E068B;
	Wed, 17 Feb 2016 20:07:52 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 96B263909E;
	Thu, 18 Feb 2016 01:07:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D833F38ED8
 for <tor-talk@lists.torproject.org>; Thu, 18 Feb 2016 01:07:43 +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 JziHyrNhAhAf for <tor-talk@lists.torproject.org>;
 Thu, 18 Feb 2016 01:07:43 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id A380538CB2
 for <tor-talk@lists.torproject.org>; Thu, 18 Feb 2016 01:07:43 +0000 (UTC)
Received: from cotinga.riseup.net (unknown [10.0.1.164])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id AEC101A1483
 for <tor-talk@lists.torproject.org>; Thu, 18 Feb 2016 01:07:40 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1455757660; bh=VFzE0gn387BrfqBECz9eMdVrh+yhjxOHujbTsEttk5E=;
 h=In-Reply-To:References:Subject:From:Date:To:From;
 b=ZJ826b883FmdYKkZDJBHDv+AsA6PY8UNhlNUk7WGH1Ejb9hefiAn7ZfdUeIrZPDjm
 G5vMpaS8BmWVwvVMuCmUgfkx/Kb/VgtV0xEZyLsZ25GO+6DUHLXN39ZY5VtiXeDt4v
 7vPaG0bHMXRCUgl/iwZoB7ZJjk5owtoiFuPKDPY4=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: flipchan) with ESMTPSA id D5C06404CC
In-Reply-To: <20160217234532.GY7734@moria.seul.org>
References: <55429155-5918-4E95-AB28-047910B30D27@riseup.net>
 <20160217234532.GY7734@moria.seul.org>
MIME-Version: 1.0
From: Flipchan <flipchan@riseup.net>
Date: Thu, 18 Feb 2016 02:07:36 +0100
To: tor-talk@lists.torproject.org
Message-ID: <FEEE68D5-A501-4DC3-8225-78B0FA5C9AE3@riseup.net>
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Bad exit/bad relay list
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>

Great! Thnks

Roger Dingledine <arma@mit.edu> skrev: (18 februari 2016 00:45:32 CET)
>On Thu, Feb 18, 2016 at 12:36:53AM +0100, Flipchan wrote:
>> Does anyone have or know where i can find a list with bad
>exits/relays
>
>There aren't great resources for this I think.
>
>The simple answer is that you can look at your cached consensus file,
>and the ones labelled BadExit are the bad exits, and the ones that are
>missing (ha) are the bad relays.
>
>If you want a way to visualize the consensus plus the votes that went
>into it, check out
>https://consensus-health.torproject.org/consensus-health.html
>(warning, it's a huge page)
>
>For a while it looks like somebody was maintaining
>https://trac.torproject.org/projects/tor/wiki/doc/badRelays
>
>But ultimately this is a really crummy arms race to play, and while I'm
>a fan of transparency for most development, it ends up making things
>too asymmetric in the wrong direction in this case:
>https://lists.torproject.org/pipermail/tor-talk/2014-July/034219.html
>
>As for reporting bad relays, see
>https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays
>
>Hope this helps,
>--Roger
>
>-- 
>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

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

