Re: /srv/bzr/emacs/trunk r105466: epa-mail.el handles GnuPG groups.

[Daiki Ueno]

Richard Stallman <address@hidden> writes:

>     There is already a function `epg-expand-group' to parse group
>     definitions.  With that, the change could be rewritten to:
>
> Would you please make the improvement you suggested?

Done.

> Parsing gpg.conf is necessary because epa tries to check the
> recipients itself before passing them to gpg.  Is there a good reason
> to check them?  Why not just pass them to gpg (first giving the user
> an opportunity to edit the list, as mailcrypt-encrypt does), then let
> gpg reject any that are not valid?

epa has a nice feature to select keys interactively, which is based on
(group-expanded) key information in elisp level.  Try:

C-u M-x epa-mail-encrypt

and you will see the list of keys which will be used to encrypt, before
doing actual encryption.  This is useful for careful users who don't
want to encrypt emails with untrusted/unwanted keys.

> This way, epa would not need to expand the groups, or know about them.
> And maybe a lot of other code could be deleted too.

The amount of code to be removed wouldn't be that much because
`epg-expand-group' uses parsed groups info provided by:

gpg --list-config --with-config

Regards,
-- 
Daiki Ueno