Skip to content

Commit

Permalink
man: Add that "GETINFO address" won't work with "Sandbox 1"
Browse files Browse the repository at this point in the history
Patch by "wagon".

Closes #28538

Signed-off-by: David Goulet <dgoulet@torproject.org>
  • Loading branch information
dgoulet-tor committed Dec 12, 2018
1 parent 4afc6b1 commit 53855d7
Showing 1 changed file with 18 additions and 13 deletions.
31 changes: 18 additions & 13 deletions doc/tor.1.txt
Original file line number Diff line number Diff line change
Expand Up @@ -598,21 +598,26 @@ GENERAL OPTIONS
Otherwise the sandbox will be disabled. The option is currently an
experimental feature. It only works on Linux-based operating systems,
and only when Tor has been built with the libseccomp library. This option
can not be changed while tor is running.
can not be changed while tor is running. +
+
When the Sandbox is 1, the following options can not be changed when tor
When the **Sandbox** is 1, the following options can not be changed when tor
is running:
Address
ConnLimit
CookieAuthFile
DirPortFrontPage
ExtORPortCookieAuthFile
Logs
ServerDNSResolvConfFile
Tor must remain in client or server mode (some changes to ClientOnly and
ORPort are not allowed). Launching new Onion Services through Control
Port is not supported with current syscall sandboxing implementation.
ClientOnionAuthDir and any files in it won't reload on HUP signal.
**Address**,
**ConnLimit**,
**CookieAuthFile**,
**DirPortFrontPage**,
**ExtORPortCookieAuthFile**,
**Logs**,
**ServerDNSResolvConfFile**,
**ClientOnionAuthDir** (and any files in it won't reload on HUP signal).
+
Launching new Onion Services through the control port is not supported
with current syscall sandboxing implementation.
+
Tor must remain in client or server mode (some changes to **ClientOnly**
and **ORPort** are not allowed). Currently, if **Sandbox** is 1,
**ControlPort** command "GETINFO address" will not work.
+
(Default: 0)

[[Socks4Proxy]] **Socks4Proxy** __host__[:__port__]::
Expand Down

0 comments on commit 53855d7

Please sign in to comment.