Delivery-Date: Wed, 29 Jul 2015 16:51:19 -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,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 4DBFB1E0241;
	Wed, 29 Jul 2015 16:51:18 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D307C3440D;
	Wed, 29 Jul 2015 20:51:11 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7F6E633F90
 for <tor-talk@lists.torproject.org>; Wed, 29 Jul 2015 20:51:08 +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 CnKn_QeDbWHV for <tor-talk@lists.torproject.org>;
 Wed, 29 Jul 2015 20:51:08 +0000 (UTC)
Received: from ccs.nrl.navy.mil (mx0.ccs.nrl.navy.mil
 [IPv6:2001:480:20:118:118::211])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 61EA633AC0
 for <tor-talk@lists.torproject.org>; Wed, 29 Jul 2015 20:51:08 +0000 (UTC)
Received: from vpn212046.nrl.navy.mil (vpn212046.nrl.navy.mil [132.250.212.46])
 by ccs.nrl.navy.mil (8.14.4/8.14.4) with ESMTP id t6TKp4dP001172
 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT)
 for <tor-talk@lists.torproject.org>; Wed, 29 Jul 2015 16:51:06 -0400
Date: Wed, 29 Jul 2015 16:51:05 -0400
From: Paul Syverson <paul.syverson@nrl.navy.mil>
To: tor-talk@lists.torproject.org
Message-ID: <20150729205105.GE75683@vpn212046.nrl.navy.mil>
References: <CADop2NGNaenBevLji14cYyD-U=awKYX_WWq1t5F9gW+1wOhYbA@mail.gmail.com>
 <20150729135051.GB19830@vpn212046.nrl.navy.mil>
 <CADop2NExQwGW9VW4bapehuof-9FhEUBSS_XzGK-tdHi6NwTtZA@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CADop2NExQwGW9VW4bapehuof-9FhEUBSS_XzGK-tdHi6NwTtZA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-CCS-MailScanner: No viruses found.
X-CCS-MailScanner-Info: See: http://www.nrl.navy.mil/ccs/support/email
Subject: Re: [tor-talk] Historically speaking,
 what was the U.S. navy /military
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 Thu, Jul 30, 2015 at 03:36:52AM +0800, Virgil Griffith wrote:
> > old at that point.)  We had a picture where the ordering
> > information went over the Web from the Pentagon to Domino's and was
> > routed by an enemy (Iraq at the time of the putative pizza channel
> > concern). I remember a point I would make during presentations was
> > that the enemy could see the number of orders made by people at the
> 
> That's a nice anecdote.  Thanks :)
> 
> 
> Also...
> 
> On Wed, Jul 29, 2015 at 9:55 PM, Alexandre Guillioud
> <guillioud.alexandre@gmail.com> wrote:
> > I had heard that the original use case were to protect their (US navy)
> > ships against command center localisation through RF harvesting. The onion
> > routing of the admiral commands through a few boats means enemmies can't
> > detect which on is giving orders.
> 
> Paul: I had heard this story as well.  Can you confirm/refute it?

I can confirm that this is the first I've ever heard that. I can also
confirm that I talked long ago (maybe late nineties or early aughts,
in any case after the first public onion routing deployments) to
someone who knows way more than I do about how communication on and
off ships at sea happens (or at least did at the time). This wasn't a
Navy or government person, just an academic researcher I know who said
he knew about this environment. I had an idea roughly the same as
described in this scenario and asked if this could be another useful
application of onion routing.  He said that the very tight constraints
of this environment made it almost certain that the multiple hops
needed would be unacceptable. I didn't pursue any further.

aloha,
Paul
-- 
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

