feat: add newnym circuit rotation and stream isolation#201
Open
UncleJ4ck wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was a problem?
There was no way to request a new circuit (a new exit IP) without a full
restart, which tears down every rule and restarts tor.How this PR fixes the problem?
Adds
nipe newnym: it talks to tor's control socket, authenticates with the cookie, sendsSIGNAL NEWNYM, waits briefly for the new circuit, then prints the new status.restartis unchanged.Two supporting changes in the same area:
nipe.plnow prints the real error in the catch block instead of a generic message, and only requires root for the commands that touch tor or iptables (statusandhelpno longer do).IsolateClientAddr IsolateClientProtocol IsolateDestAddr IsolateDestPortonTransPort(void already had it) so separate destinations do not share a circuit, and void gets the control socket and pid file the others already define.Check lists (check
xin[ ]of list items)Additional Comments (if any)
The control AUTHENTICATE line is built by a pure
auth_commandcovered byt/40-newnym.t, andt/00-compile.tloads every module. On the non-Arch distros the control socket already exists; on Arch it is added by the lifecycle PR. Verified live in an Arch container: afternipe newnymthe exit IP changes (45.66.35.35 to 185.220.101.26 in the test run).