Delivery-Date: Sun, 24 May 2015 09:54:29 -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 7461F1E09E2
	for <archiver@seul.org>; Sun, 24 May 2015 09:54:27 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C0DAB356CF;
	Sun, 24 May 2015 13:54:18 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A2846356CA
 for <tor-talk@lists.torproject.org>; Sun, 24 May 2015 13:54:13 +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 EeC0TI7r9jTj for <tor-talk@lists.torproject.org>;
 Sun, 24 May 2015 13:54:13 +0000 (UTC)
Received: from smtp5.hushmail.com (smtp5.hushmail.com [65.39.178.142])
 (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 77041356C9
 for <tor-talk@lists.torproject.org>; Sun, 24 May 2015 13:54:13 +0000 (UTC)
Received: from smtp5.hushmail.com (localhost [127.0.0.1])
 by smtp5.hushmail.com (Postfix) with SMTP id 2EA246021B
 for <tor-talk@lists.torproject.org>; Sun, 24 May 2015 13:54:10 +0000 (UTC)
Received: from smtp.hushmail.com (w5.hushmail.com [65.39.178.80])
 by smtp5.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Sun, 24 May 2015 13:54:10 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 1D39AA291E; Sun, 24 May 2015 13:54:10 +0000 (UTC)
MIME-Version: 1.0
Date: Sun, 24 May 2015 09:54:09 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <5561BE2A.7050709@gmail.com>
References: <5561B2DB.4050407@gmail.com>
 <E63D0E68-C57E-4D06-8BDA-86371F2A4785@tvdw.eu> <5561B66D.8000101@gmail.com>
 <5561B93E.3020002@sky-ip.org> <5561BE2A.7050709@gmail.com> 
Message-Id: <20150524135410.1D39AA291E@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] SOCKS proxy to sit between user and Tor?
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,

Is the Socks-to-Socks proxy absolutely necessary? This could be done
as a browser plugin couldn't it? You might find the work of the
FreeSpeechMe team interesting. They have the objective of integration
with tor which sounds a lot like what you describe. It's probably not
vetted to your standards (yet) but the source may be a start for
tinkering. 

Would I be correct in saying this offers an alternative over OnioNS in
that it:
- requires downloading the blockchain, so will not leak statistics
associated with lookups
- can be extended to a general petname system which maps personally
chosen identifiers to known onion properties

On that note: what are the advantages of namecoin (.bit to .onion)
over a petname system (id to .onion) or OnioNS?

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

