[tor-bugs] #6666 [Stem]: Stem wrapper method for the EXTENDCIRCUIT control command
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Nov 7 17:13:23 UTC 2012
#6666: Stem wrapper method for the EXTENDCIRCUIT control command
--------------------+-------------------------------------------------------
Reporter: neena | Owner: neena
Type: task | Status: assigned
Priority: normal | Milestone:
Component: Stem | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------+-------------------------------------------------------
Changes (by atagar):
* owner: atagar => neena
Comment:
This looks to now be moot due to the introduction of an ONLINE
requirement...
{{{
atagar at morrigan:~/Desktop/stem$ ./run_tests.py --integ --test
test.integ.control.controller
...
test_extendcircuit (requires online target) [SKIPPED]
}}}
Usually I run tests with 0.2.1.30 to make sure we aren't introducing
problems with older tor versions, but when I call EXTENDCIRCUIT with the
equivalent call from that stacktrace I'm not getting a 512 response.
Rather, it's a 552...
{{{
atagar at morrigan:~/Desktop/stem$ telnet localhost 9051
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
AUTHENTICATE
250 OK
GETINFO version
250-version=0.2.1.30
250 OK
EXTENDCIRCUIT 0 purpose=general
552 No such router "purpose=general"
}}}
And with tor 0.2.3.16 it's a 551...
{{{
atagar at morrigan:~/Desktop/stem$ telnet localhost 9051
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
AUTHENTICATE
250 OK
GETINFO version
250-version=0.2.3.16-alpha-dev (git-8be6058d8f31e578)
250 OK
EXTENDCIRCUIT 0 purpose=general
551 Couldn't start circuit
}}}
Maybe we should check when the 'purpose=' argument was introduced, and
have the Controller do a version check on that before trying to use it?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6666#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list