Delivery-Date: Thu, 31 Jul 2014 07:44: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.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 59D611E0670;
	Thu, 31 Jul 2014 07:44:16 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 17019309C6;
	Thu, 31 Jul 2014 11:44:09 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C77ED30828
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 11:44:04 +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 W7LFkw66BetR for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 11:44:04 +0000 (UTC)
Received: from corp.netservicesgroup.com (corp.netservicesgroup.com
 [64.113.34.13])
 by eugeni.torproject.org (Postfix) with ESMTP id A5D4930742
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 11:44:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=t-3.net; s=default;
 t=1406807044; bh=dLPz+uUPzcI+zbV115rttcuUBWB9gO9wn8TfUp+QpIA=;
 h=From:To:Subject:Date;
 b=X4C5QV1CGelleMYtsp4adTxjweGUmYJR9caSmwHPiQhoYyXiOs9xrxmaaCZeba0UV
 HSBiUe7HbZsB7ZaDuEIQPENVHoM3xbTvHPiW4GKwEIdq3dANPfVPUq6IG4z6RvWWNO
 +DdWZj6TFpVa88RS+8HsRfWheJvVOVPRXfPDu8Y8=
X-Rcpt-Trace: tor-talk at lists.torproject.org
X-Default-Received-SPF: pass (skip=forwardok (res=PASS))
 x-ip-name=64.113.32.22; 
From: tor@t-3.net
To: <tor-talk@lists.torproject.org>
Date: Thu, 31 Jul 2014 07:44:02 -0400
Message-ID: <53da2c02.4bf.4fc2d700.71f0a187@t-3.net>
MIME-Version: 1.0
X-Originating-IP: 64.113.32.22
X-Mailer: SurgeWeb - Ajax Webmail Client
X-Authenticated-User: tor@t-3.net 
X-SpamDetect: : 0.000000 
X-Vpipe: Scanner said ok (av_avast)
X-Info: aspam skipped due to (g_smite_skip_auth)
X-MyRbl: Color=Unknown ip=64.113.32.22
X-IP-stats: Incoming Last 1, First 34, in=13, out=0, spam=0 ip=64.113.32.22
Subject: Re: [tor-talk] Why make bad-relays a closed mailing 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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Actually...

A bad-relays mailing list would IMO take a degree of care to do right, 
considering that email gets gathered at the packet level by 
intelligence agencies who are expected to be initiating attacks. 
Sensitive stuff would belong as GPG or PGP emails or similar. Juicy 
details regarding bad-relays discussion should be tighter than even a 
closed mailing list, is my thought.






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

