Delivery-Date: Thu, 28 Aug 2014 15:20:05 -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 CC1AE1E0A65;
	Thu, 28 Aug 2014 15:20:03 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id F1D8B309FD;
	Thu, 28 Aug 2014 19:19:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E907B309F8
 for <tor-talk@lists.torproject.org>; Thu, 28 Aug 2014 19:19:56 +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 H7aeVMR95Giy for <tor-talk@lists.torproject.org>;
 Thu, 28 Aug 2014 19:19:56 +0000 (UTC)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com
 [IPv6:2a00:1450:4010:c03::234])
 (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 918CA30999
 for <tor-talk@lists.torproject.org>; Thu, 28 Aug 2014 19:19:56 +0000 (UTC)
Received: by mail-la0-f52.google.com with SMTP id ty20so1556619lab.11
 for <tor-talk@lists.torproject.org>; Thu, 28 Aug 2014 12:19:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arlen.io; s=google;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=cdDJusqzSGZ8X2xLpJWtB2JJbzBYxHCECSerFweo5gY=;
 b=o39TDgUzGZFOA9Tr4XrOhSB9y3VxI6YO8fLx/FOT16WpYr9nG/qYKtVM5vQHnAMote
 +7KQB6krXbSw8dTreXj997KQR61WoVVkReAIipJLpT6l2R2FrFfaBw2Iw4+NkwOgYpa/
 FNGr30TAVkV/8slUBGn5+x19HFsZmTojP6osQ=
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=cdDJusqzSGZ8X2xLpJWtB2JJbzBYxHCECSerFweo5gY=;
 b=bDoN7oK8fHuiMxQWp9IVjKLDoOlDX/hoLYBrrN3xZ+nvQtCk98AT9+VbUKYLg8oRN2
 fWaVQHpkOg1Y013rwOThSXjF4jA0tK6CZaC1c3AiCdgYulM1SvwXEVe3M12pM1g32XsU
 wTYgYZ+MCNhf+zdfWPj0Y88iqTFKrFHxmfKDGnCkttJCT93gdI+5vMxh+MuEH/46xKm4
 khUpTgcrbbtLT4a1YzxDCPLCFbN2uqPtzF38mBq/mIEZ4WHEKaXn6KyJiSGGGIEd3Hk7
 NlgJYQzNjTZwlZ+HHHxuesUNhJIooB2Lu4DYbAthPhcympploVH45jN7r/ThhM/xNXkh
 TSrA==
X-Gm-Message-State: ALoCoQmVKPDk+GZPUOPb3lfAQ6nVDMxr77MpV/G7eQJl7Kx2g1YnWqS/z7GPAcgfkr7uAfAgLuAE
MIME-Version: 1.0
X-Received: by 10.112.141.7 with SMTP id rk7mr2346840lbb.83.1409253593082;
 Thu, 28 Aug 2014 12:19:53 -0700 (PDT)
Received: by 10.25.44.19 with HTTP; Thu, 28 Aug 2014 12:19:53 -0700 (PDT)
X-Originating-IP: [68.57.105.82]
Received: by 10.25.44.19 with HTTP; Thu, 28 Aug 2014 12:19:53 -0700 (PDT)
In-Reply-To: <20140828184330.A012340E91@mail.unseen.is>
References: <20140828184330.A012340E91@mail.unseen.is>
Date: Thu, 28 Aug 2014 15:19:53 -0400
Message-ID: <CALP_Sx3_x2AEd-gaw_fgLi-HGmfjOfhpDQxsci3aeg5carD5bQ@mail.gmail.com>
From: JT Allison <tor@arlen.io>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] I have a quick question about security of tor with 3
	nodes
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>

It works like any other email you're replying to. No need to start a new
email, just reply to the one you're responding to.

---
GPG/PGP Fingerprint
E129 722B A512 105C E8BE
4705 8046 EA48 2C82 1339
https://arlen.io/key
On Aug 28, 2014 3:16 PM, "John Doe" <wedeserveprivacy@unseen.is> wrote:

> I am not sure how this all works, but I am attempting to reply in the same
> vein I started.
>
> How can I set the number of relays in the configuration file? Also can you
> explain why 3 is enough? I hear things of analysis being able to track
> people trough the various relays they use. This worries me some. Care to
> help me understand?
>
> thanks
>
> --
> John Doe <wedeserveprivacy@unseen.is>
>
> --
> 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
>
>
-- 
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

