mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-10 01:48:00 +00:00
ba4837dae8
This causes PuTTY processes spawned from its system-tray menu to run with the -restrict-acl option (or rather, the synonymous &R prefix used by my auto-constructed command lines for easier parsing). The previous behaviour of Pageant was never to pass -restrict-acl to PuTTY, even when started with -restrict-acl itself; this is not actually a silly thing to want to do, because Pageant might well have more need of -restrict-acl than PuTTY (it stores longer-term and more powerful secrets) and conversely PuTTY might have more need to _not_ restrict its ACL than Pageant (in that among the things enabled by an unrestricted ACL are various kinds of accessibility software, which is more useful on the more user-facing PuTTY than on Pageant). But for those who want to lock everything down with every security option possible (even though -restrict-acl is only an ad-hoc precaution and cannot deliver any hard guarantees), this new option should fill in the UI gap. |
||
---|---|---|
.. | ||
blurb.but | ||
chm.css | ||
config.but | ||
errors.but | ||
faq.but | ||
feedback.but | ||
gs.but | ||
index.but | ||
intro.but | ||
Makefile | ||
man-pag.but | ||
man-pg.but | ||
man-pl.but | ||
man-pscp.but | ||
man-psft.but | ||
man-ptel.but | ||
man-pter.but | ||
man-putt.but | ||
mancfg.but | ||
manpages.but | ||
pageant.but | ||
pgpkeys.but | ||
plink.but | ||
pscp.but | ||
psftp.but | ||
pubkey.but | ||
site.but | ||
sshnames.but | ||
udp.but | ||
using.but | ||
vids.but |