Delivery-Date: Sun, 02 Nov 2014 02:47:52 -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.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 2DEB51E041F;
	Sun,  2 Nov 2014 02:47:51 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 69E4D315D6;
	Sun,  2 Nov 2014 07:47:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 53405315BF
 for <tor-talk@lists.torproject.org>; Sun,  2 Nov 2014 07:47:44 +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 QN88asqkk4e3 for <tor-talk@lists.torproject.org>;
 Sun,  2 Nov 2014 07:47:44 +0000 (UTC)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com
 [IPv6:2a00:1450:4010:c03::22e])
 (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 F05D63130A
 for <tor-talk@lists.torproject.org>; Sun,  2 Nov 2014 07:47:43 +0000 (UTC)
Received: by mail-la0-f46.google.com with SMTP id hs14so7991290lab.5
 for <tor-talk@lists.torproject.org>; Sun, 02 Nov 2014 00:47:40 -0700 (PDT)
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=d8mOazGzv9L8YGX/x6KTGfysKsI9sl5shf0Bi6yvI7w=;
 b=JLaKH8fCIhdjVgjXBUmtLSPzgk494lGrP9YiCtSsT1idm1cXSuIoZyyqDsoRLjMnoq
 89IxknunyX52Z6h2NCS+CTEmX2oHllNMHCnz1fGrhnDdpxwPnvlHjN6ewfGd+nuZQiIB
 OxheihNG6AM2/CZdvMat1PB7nonsGB3cNhGr2B7uGGeUiy7iGipeJDSyf4LI6h2LH+r6
 NFyYeQe/kPoqRR8+6K+UP2p507HIL+dQInfhyfKwOgOW4UmKniMUOnAb2H9u2GqA6sC1
 kEhk46NXDZws8NV3e8pe1S7yojvfEzdvLwqjMhNFq7kZIgK5CTOtL4JqJ87pZTInY0M3
 qj1w==
MIME-Version: 1.0
X-Received: by 10.112.132.34 with SMTP id or2mr40519632lbb.75.1414914460586;
 Sun, 02 Nov 2014 00:47:40 -0700 (PDT)
Received: by 10.112.156.225 with HTTP; Sun, 2 Nov 2014 00:47:40 -0700 (PDT)
In-Reply-To: <8791008.gPgc6LIrom@ncpws04>
References: <7488606.2oxgLGVBPl@ncpws04>
 <CAJVRA1QJ26Vtjt57N4Ducw3LV=MxnqaoGj0DY6L2D4-5vq8rxw@mail.gmail.com>
 <8791008.gPgc6LIrom@ncpws04>
Date: Sun, 2 Nov 2014 00:47:40 -0700
Message-ID: <CAJVRA1THJ5urkXWVe7UgKVy5gA=1a6yQ4F1_=1v3m4Yu-pgxJw@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Cloak Tor Router
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 11/1/14, Lars Boegild Thomsen <lth@reclaim-your-privacy.com> wrote:
> ...
> No, we haven't done that yet apart from me trying to start this discussion
> here on the mailing list

ok. and thanks for running a relay and exit!



> ... [ OpenWRT is difficult to work with ]

this is true; i see you have tried to be accommodating.  more on this later,




> Currently it is really hard to keep up with OpenWrt as they are in a
> transition phase.  I actually think most will end up on Github and if/when
> it does I will probably make a proper fork on Github and use those as
> primary repositories.

please let them upgrade digests on packages then too! :)



> Doing electronics is
> like a lego kit but there will always be parts where you have to trust the
> specifications from the supplier.

indeed. perhaps better one day, how much are Intel's foundry services?
ah, we can dream...



> One example I have been thinking about a lot is my media player.
> ...  I think for a device like
> that it makes sense just to force everything it tried to do on the Internet
> through Tor...

agreed. the "initialized and always kept on Tor" mode of operation is
useful for products like these, preferably also bought in cash!



> ... The tricky part is to make a
> sensible default off-the-shelf setting that is suitable for those who do not
> know the details about Tor.

even a simple one time, "You are about to route your traffic over the
Tor network. Turn off your torrents and don't upgrade poorly written
applications".

the zero guidance to unsuspecting is what i am most concerned about;
even basic captive portal warning would be a benefit.



> This one is interesting in that I really didn't think of that at all.  I
> will need some input there.  Is that at all possible at a network level.  I
> would assume it's the bootstrap of Tor that needs to be prevented?

i have more to say on this, as there are crude and more friendly ways
to do this.  it is not the end of the world if it happens, either.
just extra slow and inefficient :)



> I was writing about this in an earlier email.  It is a little bit tricky for
> a device such as this.  I personally find it hard to accept the idea of
> fully automatic updates, but I am quite open for ideas on how to do this
> best.

agreed. another topic deserving of a full discussion.  so queued,

thanks again, i appreciate your in depth responses!


best regards,
-- 
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

