[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #14979 [Core Tor/Nyx]: Option to close circuit



#14979: Option to close circuit
--------------------------+------------------------
 Reporter:  intrigeri     |          Owner:  atagar
     Type:  enhancement   |         Status:  new
 Priority:  Low           |      Milestone:
Component:  Core Tor/Nyx  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  connections   |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------

Comment (by wagon):

 > you get an unexpected HTTPS or SSH warning, write down the info about
 your exit node, and close that circuit to get a fresh one and confirm your
 suspicions.
 You can already do it with `tor-prompt`, but it is not straightforward:
 1. Run `GETINFO stream-status` and get a number of the circuit associated
 to your SSH connection (IP or hostname will be written). It is the third
 parameter in each stream.
 2. Run `GETINFO circuit-status` and look for the circuit which has that
 circuit's number (from the step 1). It is the first parameter in each
 circuit.
 3. If you look at the line with the right circuit from the step 2, you can
 see fingerprint and nickname of your exit node (it was used for your SSH
 connection).
 4. To get more information on the exit node from the step 3, run the
 command `GETINFO ns/id/FINGERPRINT`. It will give you IP address. If you
 want to know also its country, run `GETINFO ip-to-country/IP_ADDRESS`.

 Now, if you want to change that circuit, you can either mark all already
 used circuits as dirty by typing `SIGNAL NEWNYM` command, or close only
 that particular circuit with the command `CLOSECIRCUIT CircuitNumber`,
 where CircuitNumber is taken from the step 1 (`tor` will create new
 circuit that stream automatically).

 You cannot do it with the help of the control interpreter of `nyx` because
 the bug [[https://trac.torproject.org/projects/tor/ticket/28297|#28297]]
 prevents you from learning your exit node.

 It could be done easily in `nyx` if its list of circuits include
 associated streams (somebody already proposed it in
 [[https://trac.torproject.org/projects/tor/ticket/5186|#5186]]).

 Potentially, you can create a custom circuit for your tests with the help
 of commands `EXTENDCIRCUIT`, `SETCIRCUITPURPOSE,` and `ATTACHSTREAM`, but
 if you haven't already automated this task, it may be simpler to
 temporarily fix your exit node globally (using `ExitNodes` option in
 `torrc`).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/14979#comment:4>
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