Delivery-Date: Thu, 31 Jul 2014 14:06:05 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 65C151E0BA7;
	Thu, 31 Jul 2014 14:06:03 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4F2A330ACE;
	Thu, 31 Jul 2014 18:06:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1605630AC9
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 18:05:58 +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 Otq3zUmDg8KN for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 18:05:58 +0000 (UTC)
X-Greylist: delayed 421 seconds by postgrey-1.34 at eugeni;
 Thu, 31 Jul 2014 18:05:57 UTC
Received: from jessica.everdot.org (unknown [IPv6:2001:470:1f0b:1c12::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id DE50D30AB4
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 18:05:57 +0000 (UTC)
Received: from mail.everdot.org (primail.everdot.org [IPv6:2001:470:dc2e:5::2])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by jessica.everdot.org (Postfix) with ESMTPS id B2C33FA04AA
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:58:52 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail.everdot.org (Postfix) with ESMTP id E30FE9122BD2
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:58:51 +0200 (CEST)
X-Virus-Scanned: amavisd-new at everdot.org
Received: from mail.everdot.org ([127.0.0.1])
 by localhost (everdot.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 3whDV00QPvu7 for <tor-talk@lists.torproject.org>;
 Thu, 31 Jul 2014 19:58:45 +0200 (CEST)
Received: from meilong (unknown [IPv6:2001:470:dc2e:2:79f9:998d:5cf3:37e9])
 (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.everdot.org (Postfix) with ESMTPSA id 5CA0C9122B94
 for <tor-talk@lists.torproject.org>; Thu, 31 Jul 2014 19:58:45 +0200 (CEST)
Date: Thu, 31 Jul 2014 19:58:34 +0200
From: =?ISO-8859-1?B?1nl2aW5k?= Saether <oyvinds@everdot.org>
To: tor-talk@lists.torproject.org
Message-ID: <20140731195834.7af66635@meilong>
In-Reply-To: <53da2c02.4bf.4fc2d700.71f0a187@t-3.net>
References: <53da2c02.4bf.4fc2d700.71f0a187@t-3.net>
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.24; x86_64-pc-linux-gnu)
Mime-Version: 1.0
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-Type: multipart/mixed; boundary="===============4651958505023224139=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============4651958505023224139==
Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_/CjBE34SDv5FtShRZSggDE7T"; protocol="application/pgp-signature"

--Sig_/CjBE34SDv5FtShRZSggDE7T
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

> 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=20
> intelligence agencies who are expected to be initiating attacks.=20
> Sensitive stuff would belong as GPG or PGP emails or similar. Juicy=20
> details regarding bad-relays discussion should be tighter than even a=20
> closed mailing list, is my thought.

Too bad "ContactInfo email_address" in torrc isn't "ContactInfo
email_address gpgkey" or alternatively=20

ContactEmail x@y
ContactKey numbers

There is currenctly no safe way to be contacted by the Tor gang and
this is a problem with your idea.

--Sig_/CjBE34SDv5FtShRZSggDE7T
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlPag80ACgkQNBSJHnwv/KoUxwCgoKZmOPoFnTWwBtlDCSKa5bLI
3pkAnRewlAuIKo7rY8K5iSF1wHRrDb1R
=5mLV
-----END PGP SIGNATURE-----

--Sig_/CjBE34SDv5FtShRZSggDE7T--

--===============4651958505023224139==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============4651958505023224139==--

