From: Ted Zlatanov <tzz@lifelogs.com>
Subject: encrypt.el docs and fixes
Date: Wed, 17 Jan 2007 14:44:02 -0500 [thread overview]
Message-ID: <g6964b530cd.fsf@dhcp-65-162.kendall.corp.akamai.com> (raw)
I put in some docs and fixes for encrypt.el. Please see the beginning
of the file. Let me know if you have ideas or suggestions. In the
context of Gnus, encrypt.el is a very nice way to keep all your
passwords and login info locked under one decryption password, usually
that means your ~/.authinfo. I've been using encrypt.el in Gnus for a
while with GnuPG, and it works fine. Those that know GnuPG well will
probably have ideas on improving--using the private key instead of a
password, etc. The idea for encrypt.el is to let the user choose from
any number of methods, so if you have suggestions for additional
encryption/decryption models, please let me know.
Ted
reply other threads:[~2007-01-17 19:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=g6964b530cd.fsf@dhcp-65-162.kendall.corp.akamai.com \
--to=tzz@lifelogs.com \
/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.
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 NNTP newsgroup(s).