Delivery-Date: Thu, 05 Mar 2015 04:30:51 -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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,
	URIBL_BLOCKED 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 6EEBB1E041E
	for <archiver@seul.org>; Thu,  5 Mar 2015 04:30:49 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B724920927;
	Thu,  5 Mar 2015 09:30:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3F7142138A
 for <tor-talk@lists.torproject.org>; Thu,  5 Mar 2015 09:30:42 +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 2_eYfE_s0oQ2 for <tor-talk@lists.torproject.org>;
 Thu,  5 Mar 2015 09:30:42 +0000 (UTC)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com
 [IPv6:2607:f8b0:4001:c05::22f])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 1B6BC2095F
 for <tor-talk@lists.torproject.org>; Thu,  5 Mar 2015 09:30:42 +0000 (UTC)
Received: by igkb16 with SMTP id b16so44269857igk.1
 for <tor-talk@lists.torproject.org>; Thu, 05 Mar 2015 01:30:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=nOLeKC+jdAx9PemcFwtE8qeeeYYAL3Ds33itGUdGswI=;
 b=Zu2pqxwxCwwAVK+R5zrnn2dNSjfpJ9bfOVIROLz8pCTVVF6fa7kgBQdmiikg9SL7ed
 GJn9It4rRTbZEIwE9zVBUCAH0hB/y6CkcXl8kSgS01BpAU7yEkRozEWssV3ZAQ4tAa6N
 mzwJ+KPyQxjyy3tK5MGFyVB7PZBZGyv1EumMQp849jtb1cRiDwXE6CM1ieSlDPglO6nE
 Lw/8HcRGxGyvu6Dfpa3JHBAtye4I+BHI4sFUgAQXGbf+Pi8/IUMFSAnxEI/3Ebpac33o
 4MZtR4iTRFYuq1v5n+OTMtOWkqmzOf/DUcMELJQVDiNBuQ5YAvxq/awAjTculq4WACWm
 QVKA==
MIME-Version: 1.0
X-Received: by 10.50.131.196 with SMTP id oo4mr19035437igb.2.1425547839753;
 Thu, 05 Mar 2015 01:30:39 -0800 (PST)
Received: by 10.36.111.202 with HTTP; Thu, 5 Mar 2015 01:30:39 -0800 (PST)
In-Reply-To: <87mw3s4r93.fsf@riseup.net>
References: <87mw3s4r93.fsf@riseup.net>
Date: Thu, 5 Mar 2015 04:30:39 -0500
Message-ID: <CAD2Ti2-OqvKvWf6F1AQFsPezN+X2=vhWESQwc10qL4Xmtg9=qw@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Funded search engine for onionspace?
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>

On Wed, Mar 4, 2015 at 12:16 PM, George Kadianakis <desnacked@riseup.net> wrote:
> I find their concern very valid

Respectfully... invalid. Onions are going to be mined, shared, leaked,
indexed, and copied anyways. And most certainly by your adversaries.
Do we forget merely publishing an onion to the dirs results in accesses.
Lists of onions just make all this abundantly and properly obvious for
those who don't get the picture. Nor are you going to be able to
influence or censor every list. So instead of whining they should be
doing something to enforce actual privacy...
1) HiddenServiceAuthorizeClient
2) HTTPS/app level auth
3) OpSec
4) Site defense
5) etc
-- 
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

