[tor-bugs] #6662 [Compass]: group by family
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Fri Aug 24 10:26:48 UTC 2012
#6662: group by family
-------------------------+--------------------------------------------------
Reporter: cypherpunks | Owner: karsten
Type: enhancement | Status: accepted
Priority: normal | Milestone:
Component: Compass | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by karsten):
Replying to [comment:6 cypherpunks]:
> I did some manual checks of your results, because the lines with only
two family members were not clear to me,
> but after checking them manually it was clear that the "overlapping
node" was down and therefore not showing up in the second part (merged
families) of the txt file.
>
> {{{
> 3cce3a91f6a625~8DE5 bc1245cbe16d5ee9b2~2D25 overlapping node:
A0EA6A3D1B4D30F5005E89501DB68D4E14A0E183 (down)
> AMORPHIS~4B47 KAMAGURKA~4045 overlapping node:
30CC8E08C1B2B40B37A6FAF0E1DF08C007138135 (down)
> }}}
That's true, we cannot confirm mutual family relationships if one of the
nodes is down. That means that the two families A-B and B-C cannot be
merged to A-B-C if B is down.
But that being said, I found a bug in my code where mutual checks were not
performed correctly. I
[https://trac.torproject.org/projects/tor/attachment/ticket/6662/families-2012-08-23-14-00-00-fixed.txt
attached] a fixed list based on the same consensus.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6662#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list