Delivery-Date: Mon, 11 Jan 2016 12:56:14 -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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	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 439E11E0B25;
	Mon, 11 Jan 2016 12:56:12 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9CAD32099E;
	Mon, 11 Jan 2016 17:56:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 548E020927
 for <tor-talk@lists.torproject.org>; Mon, 11 Jan 2016 17:56:04 +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 xlhhroQNsb9A for <tor-talk@lists.torproject.org>;
 Mon, 11 Jan 2016 17:56:04 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 21F03204BE
 for <tor-talk@lists.torproject.org>; Mon, 11 Jan 2016 17:56:03 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <gno-or-talk-2@m.gmane.org>) id 1aIghC-00028Y-Qh
 for tor-talk@lists.torproject.org; Mon, 11 Jan 2016 18:55:58 +0100
Received: from destiny.enn.lu ([94.242.246.23])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Mon, 11 Jan 2016 18:55:58 +0100
Received: from o.wendel by destiny.enn.lu with local (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Mon, 11 Jan 2016 18:55:58 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: tor-talk@lists.torproject.org
From: Oskar Wendel <o.wendel@wp.pl>
Date: Mon, 11 Jan 2016 17:55:49 +0000 (UTC)
Lines: 41
Message-ID: <n70qb5$m9j$1@ger.gmane.org>
References: <n6u1bd$lk2$1@ger.gmane.org> <2071581.DDH0IWsMAp@home>
 <n702af$or4$1@ger.gmane.org> <4928374.PdBrLKEJ4u@pc452>
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: destiny.enn.lu
Subject: Re: [tor-talk] Help me secure my setup
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>
MIME-Version: 1.0
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aeris <aeris+tor@imirhil.fr>:

>> I don't want to 
>> give out a correlation between time of starting the client and time of my 
>> Tor activities.
> 
> Event with always connected client, you can be correlated  :
>         online : more Tor traffic (consensus + circuit + data)
>         offline : less Tor traffic (consensus only)

You're right...

I have one more question. What are the drawbacks of not preserving Tor 
state directory between reboots? I reboot the router rarely, but it can 
happen from time to time. I run Tor from ramdisk and I don't want it to 
have any persistent storage - I want it to vanish completely as the router 
shuts down.

One drawback that I see is that after every reboot, a new entry guard will 
be selected and it can make correlation attacks easier. Maybe it would be 
wise to copy old state file during each "Tor deployment" process (by which 
I mean creating the ramdisk and copying Tor over the network to it from a 
secure machine)?

- -- 
Oskar Wendel, o.wendel@wp.pl.REMOVE.THIS
Pubkey: https://pgp.mit.edu/pks/lookup?search=0x6690CC52318DB84C
Fingerprint: C8C4 B75C BB72 36FB 94B4 925C 6690 CC52 318D B84C
-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJWk+ykAAoJEGaQzFIxjbhMExkH/2KT+L+ok21+G67IewMr4A7q
WNAwaaHKIzQePGEUImTxTNUBgUwtk45MlD0PmTgBLNcwT7FOuhJUCnl7s40Bdpk4
NfHvZYEY9xvZgm6ZQD7q62h9XN2fTSHNjR5s9Uc/EITQ7Gw+c+1UREedOgfHoSJX
GJhFNkt2yo/Ui8P4wQkOyvSrSaZHrIRONwMgUa9RAoemw8DNtyRn+mAxga/tvLzL
7Bvz/t9rrnAmv6TSot8Vw0KYt89PHeqoWcLIA1AZoc99cr5RK5GDt8oIhUFTp0BH
WlX23e6gQAAfkJcF5FVU3y5Pn+U92Gr+nPDZjDc0KbadUFKlNi59gE9ChP7//9s=
=2cYl
-----END PGP SIGNATURE-----

-- 
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

