#7619: GUARD event spec incomplete
--------------------+-------------------------------------------------------
Reporter: atagar | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor | Version:
Keywords: spec | Parent:
Points: | Actualpoints:
--------------------+-------------------------------------------------------
The spec for the GUARD event type has a few issues...
1. I'm not really sure what to expect for the 'Name' attribute. The spec
says...
{{{
Name = The (possibly verbose) nickname of the guard affected.
}}}
I've listened for some and it seems to be a fingerprint...
{{{
650 GUARD ENTRY $5D0034A368E0ABAF663D21847E1C9B6CFA09752A BAD
650 GUARD ENTRY $071C2D9D0E03D75FF30DCCA850BB29CA4A4BB383 BAD
650 GUARD ENTRY $36B5DBA788246E8369DBAF58577C6BC044A9A374 NEW
650 GUARD ENTRY $071C2D9D0E03D75FF30DCCA850BB29CA4A4BB383 GOOD
650 GUARD ENTRY $5D0034A368E0ABAF663D21847E1C9B6CFA09752A GOOD
}}}
Is this either a "$[fingerprint]" or nickname? Something else?
2. There's a TODO comment to explain the states.
3. The 'Type' is simply described as...
{{{
Type = "ENTRY"
}}}
I'm guessing that this attribute is to allow guards to be used for other
things in the future. If so then the spec should say so.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7619>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs