Delivery-Date: Sat, 12 Dec 2015 04:20:08 -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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,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 D95EC1E030D;
	Sat, 12 Dec 2015 04:20:06 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2820F38897;
	Sat, 12 Dec 2015 09:20:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4760038852
 for <tor-talk@lists.torproject.org>; Sat, 12 Dec 2015 09:19:56 +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 jU3u9jQMhR0A for <tor-talk@lists.torproject.org>;
 Sat, 12 Dec 2015 09:19:56 +0000 (UTC)
Received: from mail2.openmailbox.org (mail2.openmailbox.org [62.4.1.33])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 1CC4B3884E
 for <tor-talk@lists.torproject.org>; Sat, 12 Dec 2015 09:19:56 +0000 (UTC)
Received: by mail2.openmailbox.org (Postfix, from userid 1004)
 id B63AF2AC3417; Sat, 12 Dec 2015 10:19:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org;
 s=openmailbox; t=1449911991;
 bh=V2n8Lv7n4NnlMt77zjSXJrBZ5dCjHxmOa4yXDTD7T3w=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=brY29frIYvvPpZzKKX7D521rwakW2jtv5QUH5rDa4roJIu68xLgbTm53+ePuxrE0M
 JWdmzFjpxo3nOllp2phgDkCRUqvnCjvD9Qr1Ak1xcEGv4TYhlMEcyhQiF587VhmrJC
 eC9pKSugMJFSl4gEazr3HtYnM6GxZ6v9lqKbtRCM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org;
 s=openmailbox; t=1449911981;
 bh=V2n8Lv7n4NnlMt77zjSXJrBZ5dCjHxmOa4yXDTD7T3w=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=Z+Q+I2up9FIzO9khqBiGcsVFecXp0PUdT2NBVdZXo6yR1tDJBwJ7rzeboe3IeNhzm
 Il+2QcecBLwa+mhDS36P6fVDCnf4hyMcxZ5v86b+TATL6fQyHvcJa9DLF0PNdUX//X
 okgl3oW0wXdLxRUaLbkWQlfkGqnkv+0ny2uCeWUw=
To: tor-talk@lists.torproject.org
References: <CAKDKvuyDQCWgg65hQHb23q8R546Rsr1FU5F-qQo=NHZZj1-2kg@mail.gmail.com>
 <n4emfg$et0$1@ger.gmane.org> <566B404E.6080004@openmailbox.org>
From: nusenu <nusenu@openmailbox.org>
X-Enigmail-Draft-Status: N1110
Message-ID: <566BE6A8.8020600@openmailbox.org>
Date: Sat, 12 Dec 2015 09:19:36 +0000
MIME-Version: 1.0
In-Reply-To: <566B404E.6080004@openmailbox.org>
Subject: [tor-talk]  Does #17772 affect entry or directory guard or both?
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>

>> Tor version 0.2.7.6 fixes a major bug in entry guard selection,
>> 
>> >>     - Actually look at the Guard flag when selecting a new directory
>> >>       guard. When we implemented the directory guard design, we
>> >>       accidentally started treating all relays as if they have the Guard
>> >>       flag during guard selection, leading to weaker anonymity and worse
>> >>       performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
>> >>       by Mohsen Imani.


The changelog is not entirely clear to me, first it says "major bug in
*entry* guard selection" later it says "Actually look at the Guard flag
when selecting a new *directory* guard".

#17772 [1] is named:
"We don't consider the Guard flag when picking a *directory* guard"

Does that affect only directory guards or entry+directory guards or does
it depend on the UseEntryGuardsAsDirGuards setting which is on by default?

thanks

[1] https://trac.torproject.org/projects/tor/ticket/17772
-- 
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

