Opened at 2016-09-03T19:00:01Z
Closed at 2016-09-14T05:06:57Z
#2820 closed enhancement (fixed)
--hide-ip should turn on connections tcp=tor
Reported by: | warner | Owned by: | warner |
---|---|---|---|
Priority: | normal | Milestone: | 1.12.0 |
Component: | code-nodeadmin | Version: | 1.11.0 |
Keywords: | anonymity tor | Cc: | |
Launchpad Bug: |
Description
While manually testing tor-based client setup, I hit an extra step that I thought could be removed. While we've defined the [node] reveal-IP-address = false setting to be purely a safety flag (the only thing it can do is hit the brakes on node startup), I think it might be ok to have the --hide-ip CLI argument be more active.
In particular, I think I'd like --hide-ip to cause *two* things to happen:
- set [node] reveal-IP-address = false
- add [connections] tcp = tor
The reasoning is that:
- with reveal=false, the default tcp = tcp will be rejected
- the only other legitimate value is tcp = tor (we might add tcp = none at some point, but that'll be strictly less functional than tor)
Change History (2)
comment:1 Changed at 2016-09-13T11:40:03Z by dawuud
comment:2 Changed at 2016-09-14T05:06:57Z by Brian Warner <warner@…>
- Resolution set to fixed
- Status changed from new to closed
In 3282f2a/trunk:
Note: See
TracTickets for help on using
tickets.
made this change and added a test case; pull-request for your review here: https://github.com/tahoe-lafs/tahoe-lafs/pull/343