projects
/
elisp
/
epg.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
359180d
)
Fixed.
author
ueno
<ueno>
Fri, 21 Apr 2006 02:30:49 +0000
(
02:30
+0000)
committer
ueno
<ueno>
Fri, 21 Apr 2006 02:30:49 +0000
(
02:30
+0000)
README
patch
|
blob
|
history
diff --git
a/README
b/README
index
b438bd3
..
2627eb6
100644
(file)
--- a/
README
+++ b/
README
@@
-47,11
+47,9
@@
dumped within the core file. `read-passwd' function clears passphrase
strings by `(fillarray string 0)'. However, Emacs performs compaction
in gc_sweep phase. If GC happens before `fillarray', passphrase
strings may be moved elsewhere in memory. Therefore, passphrase
strings by `(fillarray string 0)'. However, Emacs performs compaction
in gc_sweep phase. If GC happens before `fillarray', passphrase
strings may be moved elsewhere in memory. Therefore, passphrase
-caching in Elisp is generally a bad idea. The EasyPG Library dares to
-disable passphrase caching.
+caching in Elisp is generally a bad idea.
-Fortunately, there is more secure way to cache passphrases - use
-gpg-agent.
-
-Elisp programs can set `epg-context-passphrase-callback' to cache
-user's passphrases, it is not recommended though.
+The EasyPG Library dares to disable passphrase caching. Fortunately,
+there is more secure way to cache passphrases - use gpg-agent. Elisp
+programs can set `epg-context-passphrase-callback' to cache user's
+passphrases, it is not recommended though.