Hi, You can ensure a gpg buffer doesn't leave any traces by using a minor-mode called "sensitive" which disables backups and auto-save. The code is available on the Internet, but I'll post it here if anyone is interested.
Best wishes, Colin. > Dear Jorge, > > Neat!! Thanks for providing the details. > > I've been using a somewhat similar approach with a lot less functionality > for a few years, but as I reported in the org email list, something I find > unsettling is that if an encrypted buffer is killed right when it is being > opened (when you just typed the password ---sure, low probability, but not > zero), part of the contents of the encrypted buffer are left, as plain > text, in other buffer(s). > > I reported this here > > http://lists.gnu.org/archive/html/emacs-orgmode/2011-12/msg00841.html > > and I still experience the problem (I just try it not to happen). Is > this not affecting you at all? I'd have thought it would, since you are > also using a timer to kill the buffer, and it could fire right after you > enter the password. > > > Best, > > > R. > > > On Sun, 11-05-2014, at 07:21, Jorge A. Alfaro-Murillo > <jorge.a.alf...@gmail.com> wrote: >> Hi! I have been using org for managing passwords for a some time now. In >> case someone is interested, the code is in: >> https://bitbucket.org/alfaromurillo/org-passwords.el >> >> To consult the database, the code provides a function to open the Org >> file with the passwords in Read-Only mode, sets a timer after which the >> buffer is killed and provides functions for copying the password without >> it getting into the kill-ring. It also provides two types of functions >> for generating passwords: strings of random characters, and random words >> of the correcthorsebatterystaple-type. The README file in bitbucket has >> detailed information about the usage. >> >> If there is interest from the community this can also go to /contrib. >> >> Best, >> >> Jorge. -- Colin Baxter http://www.colin-baxter.com
