Opened 6 years ago

Closed 4 years ago

#12574 closed defect (wontfix)

Include unnamed family members in family

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Normal Keywords: tor-03-unspecified-201612
Cc: Actual Points:
Parent ID: #15060 Points:
Reviewer: Sponsor:


My relay path was using two members of the same family. PPTOR0006, PPTOR0014. According to Atlas they are in the same family:

This was discussed on the tor-talk mailing list:

Roger Dingledine said:

"It looks like PTOR0014 has the Unnamed flag. I wonder if Tor clients are disregarding it because it's not named by fingerprint in the descriptor, and because it has the Unnamed flag rather than the Named flag.
Seems like a bug."

I am posting this using the public account. If you need more information you can e-mail me at soulplane11 at gmail dot com.

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by cypherpunks

Summary: Ignore unnamed family membersInclude unnamed family members in family

comment:2 Changed 6 years ago by nickm

Milestone: Tor: 0.2.???

Whenever possible, you should be specifying the other nodes in your family by fingerprint, not by name. If you specify by name, there will be inconsistent results of this kind.

Tor should really be giving a warning at startup when the family line uses nicknames. (Doesn't it do this already?)

In the long run, the solution here will probably fall out of a more general rethink of how we handle node families.

comment:3 Changed 6 years ago by nickm

Parent ID: #15060

comment:4 Changed 4 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 4 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 4 years ago by nickm

Resolution: wontfix
Severity: Normal
Status: newclosed

Authorities no longer generate the Named or Unnamed flags; this ticket is now moot.

Note: See TracTickets for help on using tickets.