From: Marcus Frings <iam-est-hora-surgere@despammed.com>
Subject: Re: PGG broken?
Date: Sun, 18 Jun 2006 17:09:20 +0200 [thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-861wtm7b6n.fsf@shodan.gothgoose.net> (raw)
In-Reply-To: <87lksgdxvt.fsf@gate450.dyndns.org>
* Andreas Seltenreich <andreas+ding@gate450.dyndns.org> wrote:
> Marcus Frings schrob:
>> * Marcus Frings <iam-est-hora-surgere@despammed.com> wrote:
>>> 1) When I use the set-policy-url option in my gpg.conf I can't sign
>>> mails anymore ("sign error"). After removing this option I can sign
>>> mails again.
> Hmm, did you really get a "sign error" signalled?[1] When I tried to
> reproduce it, I got a 'search-failed one from pgg-parse-armor, because
> pgg-gpg-sign-region returned successful signing status and an empty
> output buffer at the same time.
Yes, see
<vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86mze537am.fsf@shodan.gothgoose.net>.
> In my case, GnuPG[2] returned a non-zero exit-status because it couldn't
> generate a signature with a policy URL while maintaining PGP
> compatibility. Nevertheless, it did the signing without a policy URL
> and reported SIG_CREATED.
Yes, this is reported in the debugging buffer. See my thread mentioned
above.
> Switching PGP-compatibility off via "openpgp" in gpg.conf made the
> signing succeed with a policy URL set.
Yes, this should be a work-around. However, I'm just using a rather
simple and standard gpg.conf.
> Of course, the underdone error handling is still there, and I wonder
> if one should fix it by making the sentinel not discard the output on
> non-zero exit status, or forcing pgg-gpg to return failure even if
> there might be useful output. Anyone?
I think it's something in pgg.el because when I exchange my pgg.el from
CVS with the one from the stable release of Gnus everything works fine
again.
Regards,
Marcus
--
"Nur die halbe Welt ist Teflon und Asbest,
der Rest ist brennbar und mitunter
angezündet ganz munter anzuschaun.
So lichterloh, lichterloh und alles fuer König Feurio!"
prev parent reply other threads:[~2006-06-18 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 23:07 Signing issues with gnus from CVS Norman Walsh
[not found] ` <smuzmhfr0zb.fsf@linuxpal.mit.edu>
2006-05-18 12:30 ` Norman Walsh
2006-05-18 12:42 ` Bastien
[not found] ` <87ejyrfqsm.fsf-iS72tiDCHhS1g9c2/K602IXGvZO2VSpW@public.gmane.org>
2006-05-18 13:21 ` Jochen Küpper
2006-05-19 22:56 ` PGG broken? (was: Signing issues with gnus from CVS) Marcus Frings
2006-05-23 21:25 ` PGG broken? Marcus Frings
2006-05-24 16:10 ` Norman Walsh
2006-06-02 3:44 ` Andreas Seltenreich
2006-06-04 4:38 ` Andreas Seltenreich
2006-06-18 15:09 ` Marcus Frings [this message]
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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-861wtm7b6n.fsf@shodan.gothgoose.net \
--to=iam-est-hora-surgere@despammed.com \
--cc=protagonist@gmx.net \
/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).