Opened 13 years ago

Last modified 7 years ago

#231 closed defect (Fixed)

dirserver still serves descriptor that it ignored

Reported by: weasel Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.1.10-alpha
Severity: Keywords:
Cc: weasel Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi,

I sent a HUP to tor for some reason, which made it (among other things)
rebuild its descriptor. It never properly accepted that descriptor:
Jan 08 03:15:06.692 [info] dirserv_add_descriptor(): Not replacing descriptor from 'tor26'; differences are cosmetic.

And it also doesn't use it in network status documents:
| r tor26 hHsfhQNE14dkkaVIkvkEk05OuF0 1EU6pTJz9JND73PS0w6UXAJiChw 2006-01-07 23:01:14 86.59.21.38 443 80
(the status was published 02:26:57 UTC)

However, it still serves that new and ignored descriptor when fetching SD by identity key:
http://tor.noreply.org/tor/server/fp/847B1F850344D7876491A54892F904934E4EB85D had a
descriptor published 02:15:03 UTC.

Bug?

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (2)

comment:1 Changed 13 years ago by nickm

flyspray2trac: bug closed.
Right. Now directory authorities always believe their own descriptor.

comment:2 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.