From mboxrd@z Thu Jan 1 00:00:00 1970 From: Colin Baxter Subject: Re: An org password manager Date: Sun, 11 May 2014 14:56:58 +0100 Message-ID: <87fvkg4dw5.fsf@redstar.home> References: <87d2fklwkv.fsf@gmail.com> <87iopcad7f.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46662) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WjUX3-0000Mh-3Y for emacs-orgmode@gnu.org; Sun, 11 May 2014 10:15:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WjUWy-0000Ws-7W for emacs-orgmode@gnu.org; Sun, 11 May 2014 10:15:13 -0400 Received: from plane.gmane.org ([80.91.229.3]:55216) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WjUWy-0000W2-17 for emacs-orgmode@gnu.org; Sun, 11 May 2014 10:15:08 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WjUWu-0004zl-4D for emacs-orgmode@gnu.org; Sun, 11 May 2014 16:15:04 +0200 Received: from host81-153-143-243.range81-153.btcentralplus.com ([81.153.143.243]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 11 May 2014 16:15:04 +0200 Received: from m43cap by host81-153-143-243.range81-153.btcentralplus.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 11 May 2014 16:15:04 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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 > 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