Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T16:52:58Zhttps://gitlab.torproject.org/legacy/trac/-/issues/1922torrc.d-style configuration directories2020-06-13T16:52:58ZTractorrc.d-style configuration directoriestorrc.d-style configuration directories
**Trac**:
**Username**: aa138346torrc.d-style configuration directories
**Trac**:
**Username**: aa138346Tor: 0.3.1.x-finalJigsaw52Jigsaw52https://gitlab.torproject.org/legacy/trac/-/issues/3143Cannot avoid rogue ExitNodes2020-06-13T14:10:27ZTracCannot avoid rogue ExitNodesI am trying to avoid certain Nodes and ExitNodes which seem to be hijacking traffic and forcing an exit.
This really raises my suspicions.
For example, I have noticed that the node:
66.249.9.107 (resolves to selectresponse.com.9.249.6...I am trying to avoid certain Nodes and ExitNodes which seem to be hijacking traffic and forcing an exit.
This really raises my suspicions.
For example, I have noticed that the node:
66.249.9.107 (resolves to selectresponse.com.9.249.66.in-addr.arpa.)
will force itself to be an exit node, despite my attempts to ban it in my configuration file. I have tried using the ExcludeExitNodes and even ExcludeNodes directives, reloading the configuration of course.
I do not understand the way that circuits are built well enough to know if this is something that the client has any control over, both at the time of building the circuit or and after the circuit is built.
I have had noticed this phenomenon with a handful of other ExitNodes as well, and it obviously opens all sorts of problems if these are bad actors.
I have verified this behavior with tor clients (stable and unstable) up to version 0.2.2.25 in both linux and windows.
**Trac**:
**Username**: aa138346https://gitlab.torproject.org/legacy/trac/-/issues/1924Allow regular expression matching for ExcludeNodes/ExcludeExitNodes/EntryNode...2020-06-13T14:06:29ZTracAllow regular expression matching for ExcludeNodes/ExcludeExitNodes/EntryNodes/ExitNodesAllow regular expression matching for ExcludeNodes/ExcludeExitNodes/EntryNodes/ExitNodes, for both node name and hostname.
I understand that such a feature may not be secure.
**Trac**:
**Username**: aa138346Allow regular expression matching for ExcludeNodes/ExcludeExitNodes/EntryNodes/ExitNodes, for both node name and hostname.
I understand that such a feature may not be secure.
**Trac**:
**Username**: aa138346Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/1923Allow non-administrative users who know the HashedControlPassword to control ...2020-06-13T14:06:28ZTracAllow non-administrative users who know the HashedControlPassword to control tor client.Allow non-administrative users who know the HashedControlPassword to start/stop the tor daemon, break all existing circuits, etc., from the command line.
**Trac**:
**Username**: aa138346Allow non-administrative users who know the HashedControlPassword to start/stop the tor daemon, break all existing circuits, etc., from the command line.
**Trac**:
**Username**: aa138346Tor: unspecified