From: Simon Josefsson <jas@extundo.com>
Subject: Using epg
Date: Tue, 05 Sep 2006 12:50:27 +0200 [thread overview]
Message-ID: <87bqpu7fkc.fsf@latte.josefsson.org> (raw)
I'm trying to use epg with Gnus. First, if we are moving to epg as
the default PGG backend, how about the patch below?
Second, I get failures when signing. In *Messages* I get:
byte-code: Sign failed: ((key-expired (expiration-time 15540 . 4506)) (key-expired (expiration-time 15540 . 4506)) (key-expired (expiration-time 15540 . 4506)) (key-expired (expiration-time 15540 . 4506)) (key-expired (expiration-time 15540 . 4506)) (key-expired (expiration-time 15540 . 4506)))
I suspect it is because I have some expired keys, and EPG somehow
picked the wrong key to attempt to sign with, but I don't know how to
debug this?
FWIW, GnuPG automatically selects the right key to use, and avoids the
expired ones.
--- mml2015.el 05 Sep 2006 11:53:36 +0200 7.23
+++ mml2015.el 05 Sep 2006 12:46:09 +0200
@@ -41,6 +41,11 @@
(defvar mml2015-use (or
(progn
(ignore-errors
+ (require 'epg))
+ (and (fboundp 'epg-sign-string)
+ 'epg))
+ (progn
+ (ignore-errors
;; Avoid the "Recursive load suspected" error
;; in Emacs 21.1.
(let ((recursive-load-depth-limit 100))
@@ -59,7 +64,7 @@
(fboundp 'mc-cleanup-recipient-headers)
'mailcrypt)))
"The package used for PGP/MIME.
-Valid packages include `pgg', `gpg' and `mailcrypt'.")
+Valid packages include `epg', `pgg', `gpg' and `mailcrypt'.")
;; Something is not RFC2015.
(defvar mml2015-function-alist
next reply other threads:[~2006-09-05 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 10:50 Simon Josefsson [this message]
[not found] ` <87bqpu7fkc.fsf-Hx3HMpEclzRikQyLtWShHUB+6BGkLq7r@public.gmane.org>
2006-09-05 21:35 ` Jochen Küpper
[not found] ` <9e1wqq9eu9.fsf-X+QEHg5KIgm/8B4OpmtwqPxnRIzENc/G@public.gmane.org>
2006-09-05 21:57 ` Jochen Küpper
2006-09-06 3:29 ` Daiki Ueno
2006-09-06 9:36 ` Simon Josefsson
2006-09-06 3:34 ` Daiki Ueno
2006-09-06 7:39 ` Simon Josefsson
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=87bqpu7fkc.fsf@latte.josefsson.org \
--to=jas@extundo.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).