Delivery-Date: Wed, 06 May 2015 06:54:40 -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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,T_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 6C66F1E01B0
	for <archiver@seul.org>; Wed,  6 May 2015 06:54:38 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6F0223521E;
	Wed,  6 May 2015 10:54:34 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 01D5D35163
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 10:54:31 +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 14NLx7XmS4hh for <tor-talk@lists.torproject.org>;
 Wed,  6 May 2015 10:54:30 +0000 (UTC)
Received: from smtp2.hushmail.com (smtp2.hushmail.com [65.39.178.134])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "smtp.hushmail.com" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id D42C53515F
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 10:54:30 +0000 (UTC)
Received: from smtp2.hushmail.com (localhost [127.0.0.1])
 by smtp2.hushmail.com (Postfix) with SMTP id EA90FA012A
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 10:54:27 +0000 (UTC)
Received: from smtp.hushmail.com (w2.hushmail.com [65.39.178.46])
 by smtp2.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 10:54:27 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id BE524E04BF; Wed,  6 May 2015 10:54:27 +0000 (UTC)
MIME-Version: 1.0
Date: Wed, 06 May 2015 06:54:27 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <CAJVRA1RcFx4_FVkhws2y1f+GTNPZuf8WEyo6EMYa86vm=jQHzg@mail.gmail.com>
References: <5548D4B4.9040303@rwth-aachen.de>
 <20150505155135.GD7800@moria.seul.org>
 <20150505163624.5D57FE04BF@smtp.hushmail.com>
 <5548F685.2090704@openmailbox.org>
 <20150505170747.61F8BE04BF@smtp.hushmail.com>
 <CAJVRA1RcFx4_FVkhws2y1f+GTNPZuf8WEyo6EMYa86vm=jQHzg@mail.gmail.com> 
Message-Id: <20150506105427.BE524E04BF@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] German University signs up 24 tor relays
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>

>"Dodgson, Dodgson, we've got Dodgson here!"
 >... in other words, relays are inherently public.

What? did you actually contribute to the conversation? What the hell
does that even mean?

Fine. Relays are public. The people who operate them are public
figures too. To hell with privacy. 

HS descriptors are also public. Their operators are public figures. If
I want to create hsdirs to profile hs use and then attack hs
infrastructure that what I'll do. If that also means attacking the HS
itself to discover service weaknesses, I'll do that too. Don't like
it? Too bad. The descriptors are public.

Don't you have a glorified beagle-rasp-board to convert into a router?
Must be hard. Not like you can rely on off the shelf routers to
produce consistent lack-of-compromise.

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

