[tor-bugs] #7558 [Stem]: 'GETINFO orconn-status' unexpectedly providing ServerID rather than LongName
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Dec 9 02:40:20 UTC 2012
#7558: 'GETINFO orconn-status' unexpectedly providing ServerID rather than
LongName
---------------------+------------------------------------------------------
Reporter: eoinof | Owner: nickm
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: Stem | Version:
Keywords: testing | Parent:
Points: | Actualpoints:
---------------------+------------------------------------------------------
Changes (by rransom):
* component: Tor => Stem
Comment:
Replying to [comment:5 atagar]:
> Thanks Eoin! Reassigning this to Nick.
>
> Nick: Here's a short description of the bug...
>
> 1. Start tor 0.2.2.35 with a blank data directory, and no network
connection.
> 2. Connect to it with a controller, set VERBOSE_NAMES, then call
'GETINFO orconn-status'.
>
> Expected:
>
> orconn-status with LongName entries (ex.
"$FF70FEE26E41E0CD582C4348E78F7CACE393B299=Zwiebelschale")
>
> Actual:
>
> tor provides ServerID entries (ex.
"$F397038ADC51336135E7B80BD99CA3844360292B")
That's a LongName entry with the (optional) nickname omitted. See
[https://gitweb.torproject.org/torspec.git/blob/aeebf8950ad137478b661cc2b6fa4c47c5f88f2f
:/control-spec.txt#l169].
This is probably easiest to trigger by putting a Bridge option which
specifies a fingerprint in Tor's configuration.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7558#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list