Delivery-Date: Tue, 12 Jan 2016 09:48:58 -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 C3DF51E0C77;
	Tue, 12 Jan 2016 09:48:56 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BE03E2049B;
	Tue, 12 Jan 2016 14:48:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F1D4D37882
 for <tor-talk@lists.torproject.org>; Tue, 12 Jan 2016 14:48:48 +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 B0n7X7kLwrjF for <tor-talk@lists.torproject.org>;
 Tue, 12 Jan 2016 14:48:48 +0000 (UTC)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com
 [IPv6:2a00:1450:4010:c07::22e])
 (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 97A4F37625
 for <tor-talk@lists.torproject.org>; Tue, 12 Jan 2016 14:48:48 +0000 (UTC)
Received: by mail-lf0-x22e.google.com with SMTP id h129so40503618lfh.3
 for <tor-talk@lists.torproject.org>; Tue, 12 Jan 2016 06:48:48 -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=SsJJsVjDROhIxhBafibs/yiSwZVMRmIC2VRqI8kvo2k=;
 b=IQ1e9UzXfj45VKCqHf1EYdAZGGBBM0BXdZcW8Ci6axOIpnxjj7UyiSFufFBZwb0yCz
 YLfp353JsBEybe4o9gYf64vvN9VFUGAoBoEJZoeM1yFhvshM2RKJyxYoRf3qF/9j0eI4
 brmly8sv5iI/wNA2eF++DpbV5igd6CIu61RbLmhH/loaCyu7Am53DfCoPTDJu1Lhg/Tt
 hGdQjU9W2MSzh0FYvigfctEo+RojS7jMjTrZCgnyJMyNcVlbusQa8Ch5OqeMmtOmKpYu
 aSPQ25ScCRThJWy68Xj3tMkcYQmK5lZ2ceIp+tHTckcf7sIWkjoZlG3c3jDp0V8++Nf6
 /vRw==
MIME-Version: 1.0
X-Received: by 10.25.39.200 with SMTP id n191mr48376690lfn.7.1452610125471;
 Tue, 12 Jan 2016 06:48:45 -0800 (PST)
Received: by 10.25.87.207 with HTTP; Tue, 12 Jan 2016 06:48:45 -0800 (PST)
In-Reply-To: <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>
 <n70qb5$m9j$1@ger.gmane.org>
Date: Tue, 12 Jan 2016 15:48:45 +0100
Message-ID: <CAJVRA1TWnoTM748oYGRBFXOp0Ch90sVbo0ho3Ens85HyBqBUPA@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org
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>
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 1/11/16, Oskar Wendel <o.wendel@wp.pl> wrote:
> ...
> I have one more question. What are the drawbacks of not preserving Tor
> state directory between reboots? ...
> One drawback that I see is that after every reboot, a new entry guard will
> be selected and it can make correlation attacks easier.

this becomes particularly bad if the attacker has a way to trigger a
crash remotely  (like file descriptor exhaustion or conntrack
overflow).

placing you in attack position next to them just a simple matter of patience...

---

just save state!  if not on the router, then an encrypted volume which
requires your intervention or ambient authority to activate.


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

