Delivery-Date: Tue, 14 Oct 2014 06:37:52 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	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 18B541E0AB0;
	Tue, 14 Oct 2014 06:37:51 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 536E430E96;
	Tue, 14 Oct 2014 10:37:46 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AD11930E91
 for <tor-talk@lists.torproject.org>; Tue, 14 Oct 2014 10:37:41 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 gNdOx1OespAK for <tor-talk@lists.torproject.org>;
 Tue, 14 Oct 2014 10:37:41 +0000 (UTC)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com
 [IPv6:2a00:1450:400c:c00::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 6C55530E7A
 for <tor-talk@lists.torproject.org>; Tue, 14 Oct 2014 10:37:41 +0000 (UTC)
Received: by mail-wg0-f42.google.com with SMTP id z12so10454051wgg.1
 for <tor-talk@lists.torproject.org>; Tue, 14 Oct 2014 03:37:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=81DhVp7nasBb8xvqeTF8/YO4MiJd/S6vZnVj4angWN0=;
 b=DcWzWr8INRog9jfSQoyG7OZCpcF/z9O5S4cMmJMb0jzebiiRxejMRiHCRjQM5DChDJ
 mrdCQzuo11+2VqCR9KocPJmxory7O03xnoOsbh6SEQm+Q7ASdcaREReZ13mEYYHbOf43
 akfdCeIipcnsw+CT+GtzxKz/CWDY2rKkx4ZhNLZFxvpFIGdN3OlV6FRfy5GO3emUL9DJ
 9yhiVwlDuxqioIl7IjBoAJX4FI1JuAvnhFWer4W78k3wRfBTbt4pq/tiNSusUQO48R+V
 3S7p/mgmxZV2tVhGyOQbSzMyGXgsFaihrhuJm/bXMla1PbujNFAEA/AYk8Vmc8NixYcy
 yAyQ==
X-Received: by 10.194.23.40 with SMTP id j8mr4006596wjf.77.1413283058390;
 Tue, 14 Oct 2014 03:37:38 -0700 (PDT)
Received: from [192.168.1.11] (ANice-652-1-342-243.w83-197.abo.wanadoo.fr.
 [83.197.213.243])
 by mx.google.com with ESMTPSA id u2sm19728792wjz.11.2014.10.14.03.37.37
 for <tor-talk@lists.torproject.org>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Tue, 14 Oct 2014 03:37:37 -0700 (PDT)
Message-ID: <543CFCF3.9000805@gmail.com>
Date: Tue, 14 Oct 2014 12:37:39 +0200
From: Aymeric Vitte <vitteaymeric@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <44BDACD3189.00000851beatthebastards@inbox.com>
 <c89dfc787bb0b5459316f6baaf85022a@cryptolab.net>
 <9e34afb55dc79c67e72a35f9faa431d0@cryptolab.net>
 <CANLPe+M7utUa9Q=MzoC1E_tYkGg9WCK_ERGbAup20X8VbLkcpw@mail.gmail.com>
 <1c79d806d7a7d71f7ca3b00a10042591@cryptolab.net>
 <CANLPe+Nd+FonS8+x+DEKZB6BZmCVWBqYk01pG-_TCVu=o34j+A@mail.gmail.com>
 <CANLPe+NKhibmDDen_XUYgU_5pimjKggS0y3mTYBxWj9WRfiM5Q@mail.gmail.com>
 <c424b8605d82870689944f3378d50397@cryptolab.net>
 <CANLPe+NU2Lj+yLzGCpainEWUEQfNbWiSK=6mhrTvR5ufd5SbVQ@mail.gmail.com>
 <CAMxqorUvvphV6V0rZMAdzpf39XR4fSqdB6Fn8O2FA7o2vTG4bg@mail.gmail.com>
 <20141014075527.GC21828@loar>
In-Reply-To: <20141014075527.GC21828@loar>
Subject: Re: [tor-talk] Tor Relay Smartphone App
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


Le 14/10/2014 09:55, Lunar a =E9crit :
> Jeremy Olexa:
>> >You are abit late on the project idea:)
>> >https://www.kickstarter.com/projects/augustgermar/anonabox-a-tor-hardwa=
re-router
> If this needs repeating on this list: this is a bad idea. It will give
> people illusions instead of actual protection.

A bad idea that is doing good on Kickstarter...

I don't see very well the difference with the Onion Pi, except that it's =

unclear what code they are using or I missed it (there is a link to a 41 =

KB gz 'complete' code, this looks quite small so probably they are using =

the Tor project code) and there are no warnings about the insecure =

aspects of its use as you mentioned.

Anyway, I still think the universal solution is the javascript Tor =

protocol inside browsers, browsers would perform the Onion Proxy and =

connect to the Tor relays using WebSockets, everything that is fetched =

by a page is redirected to the WebSockets (like for example everything =

is redirected to the Socks interface when you specify it, the messages =

would be encrypted by the Onion Proxy and sent to the Tor circuits over =

WebSockets ), unfortunately while the rest exists and is working =

(node-Tor) this last point is completely undoable today.

This would work on any device, mobile or not, with the associated level =

of security because this would not eliminate the need of the Tor browser =

features and probably some confinement/security features would need to =

be studied between the page and the ws OP, maybe similar to =

http://cowl.ws/, new methods to enforce privacy inside browsers with =

principles of code confinement and labels between origins, using what =

exists today, postMessage with workers and iframes (clever use of it for =

once...)

In addtion browsers will be able to perform the OR function too, so will =

be Tor relays, as previously mentioned in this thread if the bandwidth =

of the device is bad the interest can be quasi null unless some =

multipath possibilities are available, but given the number of browsers =

in the world it could be interesting to scale Tor.

So, it's probably worth studying the possibility with browser vendors =

(and standards), ie to solve this question: how to pass all the traffic =

to a given interface (here the ws OP)?

-- =

Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

-- =

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

