Document '-restrict-acl' vs subprocesses.

(Since we've thought about it.)

diff --git a/doc/index.but b/doc/index.but
index 0375164b8a4ec8dd05bace41203b205c05ada48d..756312d515470f47815536695fa82c2a0853f3cc 100644 (file)
--- a/doc/index.but
+++ b/doc/index.but
@@ -863,3 +863,7 @@ saved sessions from
 
 \IM{64-bit Windows} 64-bit Windows
 \IM{64-bit Windows} Windows, 64-bit
+
+\IM{Windows process ACL} Windows process ACL
+\IM{Windows process ACL} process ACL (Windows)
+\IM{Windows process ACL} ACL, process (Windows)

diff --git a/doc/using.but b/doc/using.but
index b21a9a8bcb1408bb3570b620c13ffce8d821cad3..bc3ad1e5f2ab9ae39b3c38c39c5e70a5c9af6117 100644 (file)
--- a/doc/using.but
+++ b/doc/using.but
@@ -1012,15 +1012,15 @@ See \k{config-proxy-type} for more information on this, and on other
 proxy settings.
 
 \S2{using-cmdline-restrict-acl} \i\c{-restrict-acl}: restrict the
-Windows process ACL
+\i{Windows process ACL}
 
-This option (on Windows only) causes PuTTY to try to lock down the
-operating system's access control on its own process. If this
-succeeds, it should present an extra obstacle to malware that has
-managed to run under the same user id as the PuTTY process, by
-preventing it from attaching to PuTTY using the same interfaces
-debuggers use and either reading sensitive information out of its
-memory or hijacking its network session.
+This option (on Windows only) causes PuTTY (or another PuTTY tool) to
+try to lock down the operating system's access control on its own
+process. If this succeeds, it should present an extra obstacle to
+malware that has managed to run under the same user id as the PuTTY
+process, by preventing it from attaching to PuTTY using the same
+interfaces debuggers use and either reading sensitive information out
+of its memory or hijacking its network session.
 
 This option is not enabled by default, because this form of
 interaction between Windows programs has many legitimate uses,
@@ -1031,3 +1031,9 @@ up, and malware could still get in if it attacks the process between
 startup and lockdown. So it trades away noticeable convenience, and
 delivers less real security than you might want. However, if you do
 want to make that tradeoff anyway, the option is available.
+
+A PuTTY process started with \c{-restrict-acl} will pass that on to
+any processes started with Duplicate Session, New Session etc.
+(However, if you're invoking PuTTY tools explicitly, for instance as a
+proxy command, you'll need to arrange to pass them the
+\c{-restrict-acl} option yourself, if that's what you want.)