Delivery-Date: Thu, 12 Feb 2015 15:20:48 -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.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,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 C03481E0ECE
	for <archiver@seul.org>; Thu, 12 Feb 2015 15:20:46 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8FD7D333BC;
	Thu, 12 Feb 2015 20:20:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A4AD93335D
 for <tor-talk@lists.torproject.org>; Thu, 12 Feb 2015 20:20:39 +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 TLITJsPuVHbt for <tor-talk@lists.torproject.org>;
 Thu, 12 Feb 2015 20:20:39 +0000 (UTC)
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "Self-signed" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 6AB823323D
 for <tor-talk@lists.torproject.org>; Thu, 12 Feb 2015 20:20:39 +0000 (UTC)
Received: from smtp1.hushmail.com (localhost [127.0.0.1])
 by smtp1.hushmail.com (Postfix) with SMTP id ABB9040147
 for <tor-talk@lists.torproject.org>; Thu, 12 Feb 2015 20:20:35 +0000 (UTC)
Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80])
 by smtp1.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Thu, 12 Feb 2015 20:20:35 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 7B09EA0114; Thu, 12 Feb 2015 20:20:35 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 12 Feb 2015 15:20:35 -0500
To: "tor-talk" <tor-talk@lists.torproject.org>
From: "l.m" <ter.one.leeboi@hush.com>
Message-Id: <20150212202035.7B09EA0114@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [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>

Hi,

Thanks for hosting a Tor2web proxy. I think I'm using the search wrong
though. What exactly is it supposed to do? If I type in duckduckgo I
don't find a useable link to the hidden service. If I type in the
onion for duckduckgo I don't get any indication that the link is,
well, duckduckgo. To be fair a similar problem occurs with a regular
google query. On the other hand, with google itself, I can type
duckduckgo in combination with onion.cab and get a link. I'm sure I'm
using this wrong. When someone says to me, I have a search engine for
onion space, I think of typing in duckduckgo and getting results as:

- detect use of Tor and provide a link to the .onion topmost, or
redirect to the .onion if using .onion.city
- provide onion.city proxy links for everyone else that make it clear
it's the site queried
- provide alternatives to onion.city, such as the mirrors tor2web.org,
tor2web.fi, tor2web.blutmagie.de, onion.cab 

The last one seems especially important because, as was recently made
clear, an attack on an individual proxy can render it useless for
tor2web traffic. I've also read recently about how trivial it is to
get a list of google queries that correspond with client requests.
This makes me worry that a custom google query would also put this
data in the clear. Is this a custom google running in it's own rack
indexing sites? Clearnet search engines cannot access an onion so
wouldn't that make it hard for googlebot to crawl the site,
automatically, for sitemap or robots.txt? You would have to submit the
sitemap to google, and use a tor2web mirror in the address? Wouldn't
this create fragmentation in search results that only list tor2web
mirrors the crawler is aware of?

There should be more collaboration in these emerging search engines
otherwise you'll be outpaced by darpa. Note that darpa won't be
opposed to using questionable tactics in obtaining hidden service
data.

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

