Mercurial > emacs
changeset 72014:0429cbee770a
* faq.texi (Security risks with Emacs): Document Emacs 22
file-local-variable mechanism.
| author | Chong Yidong <cyd@stupidchicken.com> |
|---|---|
| date | Wed, 19 Jul 2006 02:22:51 +0000 |
| parents | 020b2d549ca8 |
| children | 93069e336ae9 |
| files | man/ChangeLog man/faq.texi |
| diffstat | 2 files changed, 11 insertions(+), 8 deletions(-) [+] |
line wrap: on
line diff
--- a/man/ChangeLog Wed Jul 19 02:19:59 2006 +0000 +++ b/man/ChangeLog Wed Jul 19 02:22:51 2006 +0000 @@ -1,3 +1,8 @@ +2006-07-18 Chong Yidong <cyd@stupidchicken.com> + + * faq.texi (Security risks with Emacs): Document Emacs 22 + file-local-variable mechanism. + 2006-07-17 Richard Stallman <rms@gnu.org> * building.texi (Grep Searching): Explain about chaining grep commands.
--- a/man/faq.texi Wed Jul 19 02:19:59 2006 +0000 +++ b/man/faq.texi Wed Jul 19 02:22:51 2006 +0000 @@ -3125,14 +3125,12 @@ Obviously, there is a potential for Trojan horses to exploit this feature. -Emacs 18 allowed this feature by default; users could disable it by -setting the variable @code{inhibit-local-variables} to a non-@code{nil} value. - -As of Emacs 19, Emacs has a list of local variables that create a -security risk. If a file tries to set one of them, it asks the user to -confirm whether the variables should be set. You can also tell Emacs -whether to allow the evaluation of Emacs Lisp code found at the bottom -of files by setting the variable @code{enable-local-eval}. +As of Emacs 22, Emacs has a list of local variables that are known to +be safe to set. If a file tries to set any variable outside this +list, it asks the user to confirm whether the variables should be set. +You can also tell Emacs whether to allow the evaluation of Emacs Lisp +code found at the bottom of files by setting the variable +@code{enable-local-eval}. For more information, @inforef{File Variables, File Variables, emacs}.