From: Daiki Ueno <ueno@unixuser.org>
Cc: ding@gnus.org
Subject: Re: Please add pgg-discard-passphrase-cache
Date: Fri, 01 Sep 2006 19:20:10 +0900 [thread overview]
Message-ID: <8ed52ad5-e407-4ee3-bdd0-cbe68042efa0@well-done.deisui.org> (raw)
In-Reply-To: <87mz9jzyvu.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 01 Sep 2006 12:04:21 +0200")
>>>>> In <87mz9jzyvu.fsf@latte.josefsson.org>
>>>>> Simon Josefsson <jas@extundo.com> wrote:
> Daiki Ueno <ueno@unixuser.org> writes:
> >>>>>> In <87veo8ymjf.fsf@latte.josefsson.org>
> >>>>>> Simon Josefsson <jas@extundo.com> wrote:
> >> Does it fully supersede all of pgg.el's features?
> >
> > As of now it only lacks PGP 2.x/5.x support, but is it still needed?
> I'm not sure. I don't care about it. Anyone else?
> Are there any advantages with epg.el over pgg.el? S/MIME support
> through gpgsm?
Yes, and other notable features,
- It provides a way to examine the verification result, which helps
verify a message signed with multiple keys.
- It can ask a user which private key to be used for encryption/sign.
- It can handle PGP messages in the binary format as well as the
ascii armor format.
- Dired integration.
- Transparent file encryption/decryption.
- Key signing.
> >> Maybe we should include it in Gnus CVS as a start?
> >
> > Please do not! There is no review process among Gnus developers and
> > someone might check his kludge in CVS without my permission.
> >
> > http://article.gmane.org/gmane.emacs.gnus.general/63038
> >
> > I don't want to repeat pgg.el mistake.
> I'd really want whatever PGP package we use to either be part of Gnus
> CVS or Emacs CVS. Automatically copying the files into Gnus CVS from
> epg.el's CVS would work fine, I think. Would that be OK? Then all
> changes to epg.el has to go through you before they hit Gnus CVS.
Since epg.el is a general purpose PGP library, I think it should be a
part of Emacs (not Gnus) from the beginning.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2006-09-01 10:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 22:05 Juliusz Chroboczek
2006-09-01 4:47 ` Daiki Ueno
2006-09-01 7:49 ` Daiki Ueno
2006-09-01 8:59 ` Simon Josefsson
2006-09-01 9:04 ` Daiki Ueno
2006-09-01 9:16 ` Simon Josefsson
2006-09-01 9:34 ` Daiki Ueno
2006-09-01 10:04 ` Simon Josefsson
2006-09-01 10:20 ` Daiki Ueno [this message]
2006-09-01 10:32 ` Simon Josefsson
2006-09-01 10:36 ` Norbert Koch
2006-09-04 8:07 ` Daiki Ueno
2006-09-01 10:38 ` Georg C. F. Greve
2006-09-01 12:14 ` Simon Josefsson
2006-09-01 12:25 ` Georg C. F. Greve
2006-09-01 13:51 ` Daiki Ueno
2006-09-01 14:15 ` Georg C. F. Greve
2006-09-01 14:43 ` Daiki Ueno
2006-09-01 15:04 ` Georg C. F. Greve
2006-09-02 1:48 ` Daiki Ueno
2006-09-02 14:15 ` Georg C. F. Greve
2006-09-01 17:10 ` Andreas Jaeger
2006-09-02 7:39 ` Juliusz Chroboczek
2006-09-04 8:57 ` Simon Josefsson
2006-09-04 9:07 ` Daiki Ueno
2006-09-13 21:28 ` Juliusz Chroboczek
2006-09-14 9:25 ` Daiki Ueno
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=8ed52ad5-e407-4ee3-bdd0-cbe68042efa0@well-done.deisui.org \
--to=ueno@unixuser.org \
--cc=ding@gnus.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.
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).