commit 894d207f844cf5fa5816432abfe8d1c02763cd59
parent 0d9dc13e087c01550e5d237f298d8a5de5994df0
Author: rl1987 <rl1987@sdf.lonestar.org>
Date: Mon, 3 Dec 2018 15:19:33 +0200
manpage: Mention that adding new HS is unsupported if Sandbox is enabled
Diffstat:
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/changes/doc28560 b/changes/doc28560
@@ -0,0 +1,3 @@
+ o Documentation (hidden service manpage, sandbox):
+ - Mention that you cannot add new Onion Service if Tor is already
+ running with Sandbox enabled. Closes ticket 28560.
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
@@ -610,7 +610,8 @@ GENERAL OPTIONS
Logs
ServerDNSResolvConfFile
Tor must remain in client or server mode (some changes to ClientOnly and
- ORPort are not allowed).
+ 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.
(Default: 0)
@@ -2821,6 +2822,8 @@ The following options are used to configure a hidden service.
Store data files for a hidden service in DIRECTORY. Every hidden service
must have a separate directory. You may use this option multiple times to
specify multiple services. If DIRECTORY does not exist, Tor will create it.
+ Please note that you cannot add new Onion Service to already running Tor
+ instance if **Sandbox** is enabled.
(Note: in current versions of Tor, if DIRECTORY is a relative path,
it will be relative to the current
working directory of Tor instance, not to its DataDirectory. Do not
