#5446 closed defect (worksforme)
tor-ctrl and Tor 0.2.3
| Reported by: | hkk | Owned by: | |
|---|---|---|---|
| Priority: | Low | Milestone: | Tor: 0.2.3.x-final |
| Component: | Core Tor/Tor | Version: | Tor: 0.2.3.12-alpha |
| Severity: | Keywords: | tor-client | |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
tor-ctrl.sh does not seem to work under 0.2.3 . Is there another way to control tor 0.2.3?
Child Tickets
Change History (5)
comment:1 Changed 7 years ago by
| Component: | Torctl → Tor Client |
|---|---|
| Milestone: | Tor: 0.2.3.x-final |
| Priority: | normal → minor |
comment:2 Changed 7 years ago by
| Milestone: | → Tor: 0.2.3.x-final |
|---|---|
| Status: | new → needs_information |
I wonder what's broken about it?
comment:3 Changed 7 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | needs_information → closed |
Works for me. Please reopen if you can answer arma's question above.
comment:4 Changed 7 years ago by
| Keywords: | tor-client added |
|---|
comment:5 Changed 7 years ago by
| Component: | Tor Client → Tor |
|---|
Note: See
TracTickets for help on using
tickets.
Reassigning since the torctl script is not part of the torctl component (it's an unfortunate naming conflict that has been left unresolved for years since none of us touch torctl.sh). Leaving this ticket open though since, if the script is truly broken, we should either fix it or finally remove it to avoid further confusion.
The most mature method for programmatically controlling a tor instance is pytorctl...
https://gitweb.torproject.org/pytorctl.git
I'm currently working on its successor, stem, but it isn't yet ready for users (help wanted)...
https://trac.torproject.org/projects/tor/wiki/doc/stem