Delivery-Date: Mon, 28 Jul 2014 20:42:07 -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_SIGNED,
	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 BD1531E0B7A
	for <archiver@seul.org>; Mon, 28 Jul 2014 20:42:02 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5A2D030287;
	Tue, 29 Jul 2014 00:42:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D62742FF2E
 for <tor-talk@lists.torproject.org>; Tue, 29 Jul 2014 00:37:32 +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 5d5juujT_raB for <tor-talk@lists.torproject.org>;
 Tue, 29 Jul 2014 00:37:32 +0000 (UTC)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com
 [IPv6:2607:f8b0:4001:c05::231])
 (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 8EC4E2FF1C
 for <tor-talk@lists.torproject.org>; Tue, 29 Jul 2014 00:37:31 +0000 (UTC)
Received: by mail-ig0-f177.google.com with SMTP id hn18so205967igb.10
 for <tor-talk@lists.torproject.org>; Mon, 28 Jul 2014 17:37:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virgil.gr; s=dkim;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=BpI/uO+QuXwxKVjfUEzhKfcjTqYsnwIUOYKBHDw1lAw=;
 b=U0dbBQUgO9zjpBLjbdDGDHWecbqJqdiyrEfAEWGwHaStVHot2Ft+BlcgjjIBpYoNn4
 g8j6+x/s4Sl0I3q5ElxEJ63iCYf9czADJluR0a3+/xgwzfM5z5aUAkIPZam+3TQ08FsE
 bUdxCzMNqr/ujQdr5BYzljQSLTSNSbe9XwApA=
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=BpI/uO+QuXwxKVjfUEzhKfcjTqYsnwIUOYKBHDw1lAw=;
 b=dWjWCs5/nSqwySTWmC6RM/k2yKNgbTjerZjPZUHpwx7f6GqhBs8QOc4tnix1izJnk4
 EN3sva3c90rn8UWTOjMoQNxoCznTZWW8dA09lOeP3G8uSLt/qmIP4At2fpTi3stkzfgx
 rUqRJYkXZVvHfkkrU5Hma3FgkhtduXlVGhYCZ5GFHYh7jpzpMVh3C4+gQiDMS4/JZ7q0
 aIqhkhMmljn64MnNM0b0UZBcmwm1SfCHT4+1Uno41Yp6BMI+K3gjn/EnIKUeDoZ3Yqxe
 nTTBg+qiBA9bpHvRf5AYach3HtZk+lUztzMbRYljRebHETMVoTDP+8CuU9xi+/JpyvGx
 6NXg==
X-Gm-Message-State: ALoCoQnq9fBKsSBa1mMVDxUzBiBXoEkPrC3kmg1RNuow7VJJ1IH4RRrzsMzApZtulpTYJ6SCf3c3
MIME-Version: 1.0
X-Received: by 10.50.114.38 with SMTP id jd6mr914982igb.25.1406594248957; Mon,
 28 Jul 2014 17:37:28 -0700 (PDT)
Received: by 10.50.134.2 with HTTP; Mon, 28 Jul 2014 17:37:28 -0700 (PDT)
In-Reply-To: <53D5F18D.1030802@riseup.net>
References: <CADop2NF77N7vqYeeCfNSPZyi1qBg8sOT2b=9DVar7qL4minJCg@mail.gmail.com>
 <53D5F18D.1030802@riseup.net>
Date: Mon, 28 Jul 2014 17:37:28 -0700
Message-ID: <CADop2NFQmhmkSqWEyeUH1htM+Ass3-Um6syW19OfjrPjJz7rZg@mail.gmail.com>
From: Virgil Griffith <i@virgil.gr>
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] What are use cases made unpleasant by Tor's speed?
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>

Mirimir, I understand you're saying faster HS-HS connections would be
jolly.  But I didnt understand exactly why.  This is to allow coordination
between hidden services?  I get that coordination between HSs is cool, but
no immediate application comes to mind.  Can you disabuse me of my
ignorance/dearth-of-creativity?

And just to be clear, Andrea's followup suggestion addresses the special
case of cooridination among HSs in which each HS is under your control?

-V



On Sunday, July 27, 2014, Mirimir <mirimir@riseup.net> wrote:

> On 07/27/2014 09:24 AM, Virgil Griffith wrote:
>
> <SNIP>
>
> > Any others that come to mind from anyone?
>
> I'm very intrigued by possibilities of multiple hidden services with
> fast HS-HS links via Tor. One use case would be the standard
> front-end/back-end website design. Another would be "smart"
> load-balancing proxies, which could detect and foil attacks such as
> DDoS, localization, and so on. Another would be full anonet-style
> darknets, using OnionCat or OpenVPN via Tor.
> --
> tor-talk mailing list - tor-talk@lists.torproject.org <javascript:;>
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>
-- 
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

