From: "Georg C. F. Greve" <greve@fsfeurope.org>
Cc: emacs-mime-ja@m17n.org, emacs-mime-en@m17n.org, ding@gnus.org
Subject: Re: EasyPG 0.0.5
Date: Mon, 04 Sep 2006 12:38:53 +0200 [thread overview]
Message-ID: <m3irk3digy.fsf@one.tarados> (raw)
In-Reply-To: <3082e72e-a7b4-41ba-aade-9c01512a6322@well-done.deisui.org> (Daiki Ueno's message of "Mon\, 04 Sep 2006 16\:39\:03 +0900")
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
Dear Daiki Ueno,
|| On Mon, 04 Sep 2006 16:39:03 +0900
|| Daiki Ueno <ueno@unixuser.org> wrote:
du> The 5th release of EasyPG is available from http://www.easypg.org.
Thanks a lot, I just installed it here and will keep trying it.
Overall, I have experienced easypg to be faster and more robust than
pgg or any of the other solutions available.
There is one problem I am experiencing, however: In FSFE we make use
of aliases that expand to several people, and we use encryption for
such groups. GnuPG provides a way to do this by adding lines
group X@Y.Z=address1@something address2@something.else ...
to the gpg.conf.
With pgg, this was never a problem, but easypg fails with
Wrong type argument: epg-key-p, nil
and that's that.
What would be the way to fix this problem?
Regards,
Georg
--
Georg C. F. Greve <greve@fsfeurope.org>
Free Software Foundation Europe (http://fsfeurope.org)
Join the Fellowship and protect your freedom! (http://www.fsfe.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 306 bytes --]
next prev parent reply other threads:[~2006-09-04 10:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 7:39 Daiki Ueno
2006-09-04 10:38 ` Georg C. F. Greve [this message]
2006-09-04 12:15 ` Daiki Ueno
2006-09-05 4:42 ` Daiki Ueno
2006-09-05 10:00 ` Georg C. F. Greve
2006-09-05 10:24 ` Daiki Ueno
2006-09-05 15:05 ` Georg C. F. Greve
2006-09-06 6:03 ` Daiki Ueno
[not found] ` <3082e72e-a7b4-41ba-aade-9c01512a6322-7dooEoSoPCYjbB9gy5Vrp2D2FQJk+8+b@public.gmane.org>
2006-09-05 21:32 ` Jochen Küpper
2006-09-06 4:04 ` 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=m3irk3digy.fsf@one.tarados \
--to=greve@fsfeurope.org \
--cc=ding@gnus.org \
--cc=emacs-mime-en@m17n.org \
--cc=emacs-mime-ja@m17n.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).