[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28676 [Core Tor/Tor]: Tor versions of Tor nodes should be accessible through ControlPort
#28676: Tor versions of Tor nodes should be accessible through ControlPort
--------------------------+----------------------------------
Reporter: wagon | Owner: arma
Type: enhancement | Status: assigned
Priority: Medium | Milestone: Tor: unspecified
Component: Core Tor/Tor | Version: Tor: 0.3.4.9
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+----------------------------------
Comment (by wagon):
> It should specify an interface too though, and that should come first,
as a patch to control-spec.txt.
It seems the exact format is not specified in
[[https://gitweb.torproject.org/torspec.git/tree/control-spec.txt|spec]]
at all:
{{{
"ns/id/<OR identity>" or "ns/name/<OR nickname>" -- the latest router
status info (v3 directory style) for a given OR. Router status
info is as given in dir-spec.txt, and reflects the latest
consensus opinion about the
router in question. Like directory clients, controllers MUST
tolerate unrecognized flags and lines. The published date and
descriptor digest are those believed to be best by this Tor,
not necessarily those for a descriptor that Tor currently has.
[First implemented in 0.1.2.3-alpha.]
[In 0.2.0.9-alpha this switched from v2 directory style to v3]
}}}
dir-spec.txt also doesn't describe what `ControlPort` must return.
> I'd be glad to take a patch for this.
Unfortunately, due to lack of knowledge I cannot make it.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28676#comment:3>
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