Delivery-Date: Tue, 05 May 2015 12:36:37 -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 028241E04F8
	for <archiver@seul.org>; Tue,  5 May 2015 12:36:34 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 578B034E16;
	Tue,  5 May 2015 16:36:31 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9DDBB34BEA
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 16:36:27 +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 eZIVQuZiqxlv for <tor-talk@lists.torproject.org>;
 Tue,  5 May 2015 16:36:27 +0000 (UTC)
Received: from smtp10.hushmail.com (smtp10.hushmail.com [65.39.178.143])
 (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 6A97934BC3
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 16:36:27 +0000 (UTC)
Received: from smtp10.hushmail.com (localhost [127.0.0.1])
 by smtp10.hushmail.com (Postfix) with SMTP id 6C74DC03E9
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 16:36:24 +0000 (UTC)
Received: from smtp.hushmail.com (w2.hushmail.com [65.39.178.46])
 by smtp10.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 16:36:24 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 5D57FE04BF; Tue,  5 May 2015 16:36:24 +0000 (UTC)
MIME-Version: 1.0
Date: Tue, 05 May 2015 12:36:24 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <20150505155135.GD7800@moria.seul.org>
References: <5548D4B4.9040303@rwth-aachen.de>
 <20150505155135.GD7800@moria.seul.org> 
Message-Id: <20150505163624.5D57FE04BF@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>

I'm not trying to upset anyone but do we really have to stalk every 
researcher who adds relays? Honestly, does there need to be a report
on  x-number of relays were added, constituting a spike this month to
date? I  mean this purely out of respect for tor-related research
worldwide.  Engaging in tor related research means they have the
ability and mentor  to identify the reason they're not getting x-flag
is because of reasons  ___, ___, and most likely ___. They know
there's resources available to pose questions if their mentor cannot
provide one. Does every tor researcher have to  disclose their
research before it's time? It's a little bit rude to assume they don't
understand the spec.

What if their research involves studying the traffic at an exit. What
if their research involves studying exploits? Yes, I know it's
questionable. This is science and engineering though. As a graduate it
wouldn't be fair to assume there wouldn't be a disclosure of results.
Have they done something wrong that they need feedback. Did they ask
for it (yet)? They aren't responsible as a graduate with a mentor?

If they're a master's student in Germany they'd have to be hiding
under a rock to not know the state of wiretapping by state
intelligence.

A little patience would be more becoming of a not-for-profit
organization that promotes privacy and anonymity. I do research too,
ongoing even, should I disclose everything to date too. Honestly. Let
them be until they're ready.

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

