Delivery-Date: Thu, 06 Nov 2014 08:41:22 -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 B77821E0518;
	Thu,  6 Nov 2014 08:41:20 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 02A00314F8;
	Thu,  6 Nov 2014 13:41:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id CA18B31378
 for <tor-talk@lists.torproject.org>; Thu,  6 Nov 2014 13:41: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 Z2OKWtWit6ha for <tor-talk@lists.torproject.org>;
 Thu,  6 Nov 2014 13:41:13 +0000 (UTC)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com
 [IPv6:2a00:1450:4010:c04::22b])
 (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 6659D3136C
 for <tor-talk@lists.torproject.org>; Thu,  6 Nov 2014 13:41:13 +0000 (UTC)
Received: by mail-lb0-f171.google.com with SMTP id b6so910755lbj.16
 for <tor-talk@lists.torproject.org>; Thu, 06 Nov 2014 05:41:09 -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=SI7GRIemC87DpbmKRIp17m9JNJZoU4B52Y8Lp3pQ7JE=;
 b=yPgEstuwbH5e/sVO9nlm/w3fWRKRuA5GZX0+izTvQ5J0UJF1+8965N9++NEAPr2zgM
 oJtBl6MDCnjUQuhE6Lr8kse4UVm+Rx9X/GKlHG/2DezuK60ecB1WbR7qjrDIvUuRUqq9
 CDMBK68MobLPnpabjBVuJCXZHH7r81V/z/4wCszvD2efnyQutT5aizsibBexSgP3OaqT
 hWCLfsGZ/0EMrrLkWRpta+vJYRN9XNfjn7m+aH/DXVZPOSvSTBCVXRIW82TJZ2dJXIer
 eFkGJ4TrIEcgGb9YOd6iWd20KOGBb4+UVMOMnlzxeJfyCabEN+CtSw7bKNoFoc/idYjs
 Ia/g==
MIME-Version: 1.0
X-Received: by 10.152.206.68 with SMTP id lm4mr5249757lac.2.1415281269801;
 Thu, 06 Nov 2014 05:41:09 -0800 (PST)
Received: by 10.112.156.225 with HTTP; Thu, 6 Nov 2014 05:41:09 -0800 (PST)
In-Reply-To: <3413830.AxW13VOK2Y@ncpws04>
References: <7488606.2oxgLGVBPl@ncpws04> <8791008.gPgc6LIrom@ncpws04>
 <CAJVRA1THJ5urkXWVe7UgKVy5gA=1a6yQ4F1_=1v3m4Yu-pgxJw@mail.gmail.com>
 <3413830.AxW13VOK2Y@ncpws04>
Date: Thu, 6 Nov 2014 05:41:09 -0800
Message-ID: <CAJVRA1T0PavAjqtT=oZ6ew5OwDi6djnDLaQ9G8Mjzm0kHONg2w@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/4/14, Lars Boegild Thomsen <lth@reclaim-your-privacy.com> wrote:
> ...
> I will definitely look into this one.  This should be quite easy to
> implement by messing a bit with the firewall tables :)
>
> Only problem I see is that to make it useful I think it would have to time
> out at some point.

in the past i have used OUI prefix lists to avoid known bad behavior.
(this doesn't work if a device is spoofing MAC of course, but in that
case they are probably savvy :)

https://standards.ieee.org/develop/regauth/oui/oui.txt

a few hundred prefixes to opt-in safe (captive unless masked avoid),
 half that to fail open on occasion (default no captive unless known usable)



> Number of wireless networks are not an issue so I _am_ beginning to think
> that more than two is necessary.  For example:
>
> 1. Open - Open network - no Tor
> 2. Transparent proxy - all tcp traffic allowed - forced through Tor -
> everything on separate circuits  - captive warning
> 3. Transparent proxy as 2 minus captive portal (for gadgets or someone who
> know what they are doing)
> 4. Isolating proxy - only https allowed - forced through Tor - everything on
> separate circuits and everything else blocked

the timeout behavior, perhaps you could detect "brain-dead re-attempt
repeat" behavior for this duration, and then let through instead.

this came up in past discussions about a device that is simply
connected but idle, not yet seen by human.  and a device that is
headless dumb, like your media player.

more feedback when i have time.

thanks again for the open discussion!

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

