Delivery-Date: Thu, 04 Feb 2016 12:17:30 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 1C0CE1E0520;
	Thu,  4 Feb 2016 12:17:28 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 366293996D;
	Thu,  4 Feb 2016 17:17:25 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4F1D339896
 for <tor-talk@lists.torproject.org>; Thu,  4 Feb 2016 17:17:21 +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 RnnnE1nKo8yI for <tor-talk@lists.torproject.org>;
 Thu,  4 Feb 2016 17:17:21 +0000 (UTC)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com
 [IPv6:2a00:1450:4010:c07::22a])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id E200039817
 for <tor-talk@lists.torproject.org>; Thu,  4 Feb 2016 17:17:20 +0000 (UTC)
Received: by mail-lf0-x22a.google.com with SMTP id m1so41474878lfg.0
 for <tor-talk@lists.torproject.org>; Thu, 04 Feb 2016 09:17:20 -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=odSlIJHYxbshLM4FBaQ1pfyC/eIHzwKp9bF7VW5A8ps=;
 b=eKgTx+zvpuNgHEDD4vlbaXJ3uZes6pUUfsvKUriAKbHS/G32zXXkRAcU0xwU34W77J
 JarKu5VsH+YZPdonFpIfLa25t91IQgcIxbFQnjH2xMTGolZjSFfgTy3amoaqVNc7GTvT
 qtsaCFpckt4uDoxP55RDh9Jh2DMgJovnaaY3bU6K9OxIGoM13gCR5rm+U8lKyazGHR6K
 O1Hz7GsG5dE4MG43s4+xFyzAYcCUXsBOUfPL+pvyBOLvvrheqroBQsZtuo8ePVqXc7o2
 6u9qhJ2Qiu337g4v0p6AOHJlEXCXc9NJZbouraldXbwNYBCb8tQNyTFosqrcDZmjIYfD
 6OgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:content-type;
 bh=odSlIJHYxbshLM4FBaQ1pfyC/eIHzwKp9bF7VW5A8ps=;
 b=Z8RTkSI9/ZQkMhvXRwG3iOag7U/9rFLJXQ66f2Xc1mqd9jcW764BxcprRG9zFBJ2E2
 kGKfsL6QcCZWlzSpz4FNtze9dNgfJ5jaVb45mnEerxSj4LYPhNWLI00fnsAkJ9nK2Gsm
 wSoYm0vVg1Z8Ra4IGOID4v87Gs2FrUagwYN3WGsztsgnot8Q+PEsvPm0ZRxGSr9We3QG
 JDKQoUmWtcOKqTXpRtoVSNUOCzycJtkl2cYELbf3rS2ick9PARmnaSneYKxt6eU5PYb4
 h1ACO6kZpyeCuDyop7bj73GP3Oqh2AFsBFfIbDAmAKEwad8U1nmHA6w4uVkQdQzxTDCr
 lmtw==
X-Gm-Message-State: AG10YOQZ/Z26/AgDf6zt0jjdMoBs2JjQWsb7ErDl7gMJnM0+NKBMlHOSVBu82hj+nClC3ww60CQd+OffVxEYow==
MIME-Version: 1.0
X-Received: by 10.25.138.194 with SMTP id m185mr3974982lfd.67.1454606237850;
 Thu, 04 Feb 2016 09:17:17 -0800 (PST)
Received: by 10.25.87.202 with HTTP; Thu, 4 Feb 2016 09:17:17 -0800 (PST)
In-Reply-To: <BL2PR08MB1786BB7A0C5D1A9B33B28C69CD00@BL2PR08MB178.namprd08.prod.outlook.com>
References: <BL2PR08MB1786BB7A0C5D1A9B33B28C69CD00@BL2PR08MB178.namprd08.prod.outlook.com>
Date: Thu, 4 Feb 2016 18:17:17 +0100
Message-ID: <CAJVRA1Se3Dho+Fyp13pQuO0xri7ACnCdpboEPrmtLVKaBB5TdQ@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Using SDR
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 2/3/16, Jeremy Rennicks <jwr4@pct.edu> wrote:
> Would it be worthwhile or feasible to route Tor traffic through SDR.. For
> example if I were a node on Tor and data came to my system would routing it
> through my SDR to another system then back over the ISP backbone add
> anonymity or be of any use?


where i have wanted SDR most is for wide area digital broadcast of Tor
consensus, for example, along with extended descriptor information,
perhaps over DVB-T bands adopted for the purpose (like the Sweedish
experiments?)

in terms of observability, it may actually be worse to use SDR links
unless they also provide strong authenticity and privacy guarantees at
the physical layer - WirelessWarrior discusses this in talks and
cypherpunks.

an interesting idea, even if not near-term practical :)


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

