aboutsummaryrefslogtreecommitdiffstats
path: root/doc/emacs/custom.texi
diff options
context:
space:
mode:
authorChong Yidong <[email protected]>2012-01-09 15:48:51 +0800
committerChong Yidong <[email protected]>2012-01-09 15:48:51 +0800
commit1de76afef25d814c84b37045b229326d02915d80 (patch)
tree2be69192b0b3b03bdff0c8e4cc878bf668820a1e /doc/emacs/custom.texi
parent6a43ef8e8508df7d732e639ec75f657f4363e27a (diff)
* lisp/custom.el (custom-safe-themes): Use SHA-256 for hashing.
* doc/emacs/custom.texi (Custom Themes): Switched custom-safe-themes to use SHA-256.
Diffstat (limited to 'doc/emacs/custom.texi')
-rw-r--r--doc/emacs/custom.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index 1d75be4dd8..82a63996a6 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -598,7 +598,7 @@ the theme file and asks if you really want to load it. Because
loading a Custom theme can execute arbitrary Lisp code, you should
only say yes if you know that the theme is safe; in that case, Emacs
offers to remember in the future that the theme is safe (this is done
-by saving the theme file's SHA1 hash to the variable
+by saving the theme file's SHA-256 hash to the variable
@code{custom-safe-themes}; if you want to treat all themes as safe,
change its value to @code{t}). Themes that come with Emacs (in the
@file{etc/themes} directory) are exempt from this check, and are