From: Colin Baxter <m43cap@yandex.com>
To: emacs-orgmode@gnu.org
Subject: Re: An org password manager
Date: Mon, 12 May 2014 15:35:10 +0100 [thread overview]
Message-ID: <87zjin6p5t.fsf@redstar.home> (raw)
In-Reply-To: 87ha4v9znr.fsf@gmail.com
Dear Ramon,
Yes. The first URL gives the lisp code.
I could never get sensitive mode to turn on by default for files having
gpg or cpt extensions. Consequently, I just "M-X sensitive RET" for each
file. To remind me, I put "sensitive" at the beginning of the file. You
may have better luck.
Best wishes,
Colin.
> Dear Colin,
>
>
>
> On Sun, 11-05-2014, at 15:56, Colin Baxter <m43cap@yandex.com> wrote:
>> 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.
>
> Thanks, I did not know about that, but I think google found it. Are you
> referring to
>
> http://anirudhsasikumar.net/blog/2005.01.21.html
>
> which was also mentioned in, say,
>
> http://stackoverflow.com/questions/482256/is-there-an-emacs-variable-to-turn-off-backup-of-files-with-a-specific-extension
>
>
> Best,
>
>
> R.
>
>
>>
>> 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.alfaro@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
next prev parent reply other threads:[~2014-05-12 14:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 5:21 An org password manager Jorge A. Alfaro-Murillo
2014-05-11 5:47 ` Igor Sosa Mayor
2014-05-11 9:15 ` Ramon Diaz-Uriarte
2014-05-11 13:56 ` Colin Baxter
2014-05-12 8:20 ` Ramon Diaz-Uriarte
2014-05-12 14:35 ` Colin Baxter [this message]
2014-05-12 22:12 ` Ramon Diaz-Uriarte
2014-05-13 11:51 ` Colin Baxter
2014-05-13 12:40 ` Jorge A. Alfaro-Murillo
2014-05-14 10:01 ` Colin Baxter
2014-05-16 13:03 ` Ramon Diaz-Uriarte
2014-05-11 17:13 ` Jorge A. Alfaro-Murillo
2014-05-11 17:20 ` Jorge A. Alfaro-Murillo
2014-05-12 8:22 ` Ramon Diaz-Uriarte
2014-05-12 20:51 ` Cayetano Santos
2014-05-21 7:32 ` Bastien
2014-05-21 11:53 ` Michael Albinus
2014-06-05 14:36 ` Jorge A. Alfaro-Murillo
2014-06-06 9:39 ` Michael Albinus
2014-05-31 16:09 ` Jorge A. Alfaro-Murillo
2014-06-01 19:17 ` Bastien
2014-06-02 17:38 ` Bastien
2014-06-02 17:53 ` Jorge A. Alfaro-Murillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjin6p5t.fsf@redstar.home \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).