Opened 2 years ago

Last modified 2 years ago

#21525 new defect

Bootstrapping authorities sometimes expect a vote valid-after time of 0

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Minor Keywords: triaged-out-20170308, tor-dirauth needs-investigation
Cc: Actual Points:
Parent ID: #21573 Points: 1
Reviewer: Sponsor:

Description

Rejecting vote from 127.0.0.1 with valid-after time of 2017-02-22 05:41:00; we were expecting 1970-01-01 00:00:001

This doesn't stop them from bootstrapping, but I wonder if it could ever become a problem?

Child Tickets

Change History (5)

comment:1 Changed 2 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.1.x-final

That sure does sound like a bug to me; let's investigate a bit further so we know why this happens.

comment:2 Changed 2 years ago by teor

Parent ID: #21573

comment:3 Changed 2 years ago by nickm

Keywords: triaged-out-20170308 added
Milestone: Tor: 0.3.1.x-finalTor: unspecified

Deferring all 0.3.1 tickets with status == new, owner == nobody, sponsor == nobody, points > 0.5, and priority < high.

I'd still take patches for most of these -- there's just nobody currently lined up to work on them in this timeframe.

comment:4 Changed 2 years ago by dgoulet

Keywords: tor-dirauth added; tor-auth removed

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

comment:5 Changed 2 years ago by nickm

Keywords: needs-investigation added
Note: See TracTickets for help on using tickets.