From: Leo <sdl.web@gmail.com>
To: ken manheimer <ken.manheimer@gmail.com>
Cc: Daiki Ueno <ueno@unixuser.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Suggestion for epa-mail-mode
Date: Wed, 22 Dec 2010 05:39:51 +0000 [thread overview]
Message-ID: <m1tyi69xi0.fsf@cam.ac.uk> (raw)
In-Reply-To: <AANLkTikF=8qLcQZrGs-1UfoYTCy343atg=3sCt1P=+ea@mail.gmail.com> (ken manheimer's message of "Mon, 20 Dec 2010 17:52:16 -0500")
On 2010-12-20 22:52 +0000, ken manheimer wrote:
> thanks, leo. i'm genuinely sorry it took so long.
Is it? The key is it is done ;)
> in fact, there were some substantial features i had to trade-off in
> the transition. allout is more cumbersome and error-prone for dealing
> with symmetric encodings for numerous encrypted entries in a file,
> because i had to let go of encryption passphrase validation and
> hinting. that comes in exchange for significantly less insecurity due
> to no handling of passphrases in emacs code. instead, as always when
> using epg with GnuPG version 2, all passphrase handling is outside of
> emacs, in gnupg's gpg, gpg-agent, and pinentry, which i expect are
> drastically less vulnerable.
>
> it is for that reason that i was ultimately willing to forego those
> features, though i wish i could have more control without greater
> vulnerability...
Many thanks for the hard work. That looks like good compromise.
> ken
Best,
Leo
next prev parent reply other threads:[~2010-12-22 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 2:53 Suggestion for epa-mail-mode Richard Stallman
2010-07-26 3:26 ` Daiki Ueno
2010-07-26 4:27 ` Werner LEMBERG
2010-07-26 5:27 ` Daiki Ueno
2010-07-26 11:55 ` Leo
2010-07-26 15:12 ` ken manheimer
2010-12-20 22:22 ` Leo
2010-12-20 22:52 ` ken manheimer
2010-12-22 5:39 ` Leo [this message]
2010-07-27 16:57 ` Richard Stallman
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=m1tyi69xi0.fsf@cam.ac.uk \
--to=sdl.web@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ken.manheimer@gmail.com \
--cc=rms@gnu.org \
--cc=ueno@unixuser.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.