Delivery-Date: Sun, 17 Aug 2014 02:35:25 -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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,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 0514A1E0ACC;
	Sun, 17 Aug 2014 02:35:23 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9B07D30800;
	Sun, 17 Aug 2014 06:35:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 8D148307D5
 for <tor-talk@lists.torproject.org>; Sun, 17 Aug 2014 06:35:15 +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 x2Vw0xjipa3i for <tor-talk@lists.torproject.org>;
 Sun, 17 Aug 2014 06:35:15 +0000 (UTC)
Received: from mail-wi0-x244.google.com (mail-wi0-x244.google.com
 [IPv6:2a00:1450:400c:c05::244])
 (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 478212C6F3
 for <tor-talk@lists.torproject.org>; Sun, 17 Aug 2014 06:35:15 +0000 (UTC)
Received: by mail-wi0-f196.google.com with SMTP id ho1so1015638wib.7
 for <tor-talk@lists.torproject.org>; Sat, 16 Aug 2014 23:35:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=2OqlAzgbrp+bxlNaAeJ0r5Ce/l+ItwfJa3HrYymK/Aw=;
 b=e8nuSVy3OOtS9+2tKZdB93O75g8Uq/dupUVQvNfxVb/GkdfmMzGJwn4pmRWppRkUA9
 Bm3pbKzr4YIpoabAkkxb0POvTMORuHQceIXdc8EMC2JxM36XscevGP87zcs9CInotNGi
 hSNxzd3W8X02X+nPL2SXgoVXJn/f2QgtPoIYHaHsxC6P1l/wmcA05shN8cP1rrD08NXR
 jW0ZpAm+mnuggDFH5mD7LTgj/Cz9nPFH1g2SMhFOpBL8gKrEILu5+As+zov+JXe3k/se
 e9f6B3i0RsiPLXK6a1z2IoPdK7PZ6UrtOPWzC6Cx2g4f68GApkZzHvCupF0RVYtR5AeS
 3ANw==
X-Received: by 10.194.76.133 with SMTP id k5mr33575104wjw.28.1408257312161;
 Sat, 16 Aug 2014 23:35:12 -0700 (PDT)
Received: from [192.168.2.129]
 (dslb-188-100-167-151.188.100.pools.vodafone-ip.de. [188.100.167.151])
 by mx.google.com with ESMTPSA id kt3sm31949766wjb.37.2014.08.16.23.35.10
 for <tor-talk@lists.torproject.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sat, 16 Aug 2014 23:35:11 -0700 (PDT)
Message-ID: <53F04D1C.2040006@googlemail.com>
Date: Sun, 17 Aug 2014 08:35:08 +0200
From: "Sebastian G. <bastik.tor>" <bastik.tor@googlemail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20140816194615.30FE5C032C@cappadocicum.torproject.org>
 <53EFC56D.8040808@googlemail.com>
 <5356AF2C-485C-429A-B8F5-9AF3C5878C87@sebastianhahn.net>
In-Reply-To: <5356AF2C-485C-429A-B8F5-9AF3C5878C87@sebastianhahn.net>
Subject: Re: [tor-talk] [tor-consensus-health] Consensus issues
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>

17.08.2014, 00:27 Sebastian Hahn:

@Damian Johnson (to avoid sending two emails)

I wouldn't have worried either if I wouldn't have found it strange to
see the notice for tor26. Please read on below.

> thanks for looking after the network!

The doctor is doing that for me. I just wanted to figure out if its
diagnose is correct.

Thank you for operating gabelmoo, thank you for your support, thank you
for...

> On 16 Aug 2014, at 22:56, Sebastian G. <bastik.tor> wrote:
>> On Sat, 16 Aug 2014 19:46:15 +0000 (UTC) the doctor said:
>>> NOTICE: Consensus belonging to maatuska was missing the following authority signatures: tor26
>>> NOTICE: Consensus belonging to tor26 was missing the following authority signatures: tor26
>>> NOTICE: Consensus belonging to urras was missing the following authority signatures: tor26
>>> NOTICE: Consensus belonging to dizum was missing the following authority signatures: tor26
>>> NOTICE: Consensus belonging to gabelmoo was missing the following authority signatures: tor26
>>> NOTICE: Consensus belonging to moria1 was missing the following authority signatures: tor26
>>> NOTICE: Consensus belonging to dannenberg was missing the following authority signatures: tor26
>>> NOTICE: Consensus belonging to Faravahar was missing the following authority signatures: tor26
>>
>> If I understand this messages correctly tor26 didn't sign the consensus
>> of any other authority. (Correct me if I'm wrong.)
>>
>> How is it possible that tor26 doesn't sign its own consensus?
> 
> Here's an easy theory on what might have happened: When it was time to
> vote, tor26 made a vote, and distributed it to the other dirauths. When
> it was done doing so, it went offline. The other dirauths made a
> consensus, and signed it. tor26 came back online, learned that there was
> a consensus it didn't know about, fetched it from the other dirauths,
> but didn't sign it - because the time to sign it was in the past. This
> does not constitute an error condition for tor26, because enough other
> dirauths signed it for it to be considered valid.

That appears to be logical. This is also in line with what I believed to
know about how the consensus is formed.

It was indeed the wording of the notice line(s) that made me believe a
consensus of an authority would somehow be bound to that authority.

> I'd argue against increasing the complexity of the voting process to
> handle this rare edge case. I do think maybe the wording is confusing:
> What does "Consensus belonging to" mean? A consensus doesn't belong to
> any individual dirauth. I don't have a quick suggestion for what to
> name the notice instead, tho.

Attention Damian Johnson ;)

How about "Consensus fetched from ..." or "Consensus downloaded from..."?

(If that requires discussion I happily open a ticket)

I don't see any benefit (at first glance) to change (and most likely
increase complexity) the voting/signing process. Especially since the
consensus is valid and it is expected to be fetchable from any authority.

>> A similar message was send on the 15th for gabelmoo, but gabelmoo had no
>> notice line. There were two warning, first gabelmoo did not publish a
>> fresh consensus and secondly it did not report bandwidth scanner
>> results. Nothing I would have worried about. Nor would I have found strange.
> 
> Yes, gabelmoo was down as I was fixing its bw auth. Nothing to worry
> about indeed.
> 
>> However an authority handing out a consensus it didn't sign might be
>> something that isn't quite right.
> 
> I think it's OK, considering the above.

When it is what it appears to be then I agree.

Thank you both for your replies-

> Cheers
> Sebastian
Sebastian G.


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

