mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-10 09:58:01 +00:00
e22120fea8
As documented in bug 'win-process-acl-finesse', we've had enough assorted complaints about it breaking various non-malicious pieces of Windows process interaction (ranging from git->plink integration to screen readers for the vision-impaired) that I think it's more sensible to set the process back to its default level of protection. This precaution was never a fully effective protection anyway, due to the race condition at process startup; the only properly effective defence would have been to prevent malware running under the same user ID as PuTTY in the first place, so in that sense, nothing has changed. But people who want the arguable defence-in-depth advantage of the ACL restriction can now turn it on with the '-restrict-acl' command-line option, and it's up to them whether they can live with the assorted inconveniences that come with it. In the course of this change, I've centralised a bit more of the restriction code into winsecur.c, to avoid repeating the error handling in multiple places. |
||
|---|---|---|
| .. | ||
| blurb.but | ||
| chm.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 | ||