From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
Subject: Re: PGG broken?
Date: Sun, 04 Jun 2006 06:38:16 +0200 [thread overview]
Message-ID: <87bqt91qo7.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <87lksgdxvt.fsf@gate450.dyndns.org> (Andreas Seltenreich's message of "Fri, 02 Jun 2006 05:44:54 +0200")
Andreas Seltenreich <andreas+ding@gate450.dyndns.org> writes:
> 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.
[...]
> 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've studied the code on the trunk a bit more, and discovered another
major issue: The usage of the same file descriptor for commands and
data fails horribly in some places. This is responsible for the rest
of the bugs I managed to reproduce.
ISTM both problems have already been identified and fixed two months
ago, but didn't make it into the No Gnus CVS:
<http://permalink.gmane.org/gmane.emacs.devel/52470>
<http://www.unixuser.org/~ueno/pgg-20060407.tar.gz>
next prev parent reply other threads:[~2006-06-04 4:38 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 [this message]
2006-06-18 15:09 ` Marcus Frings
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=87bqt91qo7.fsf@gate450.dyndns.org \
--to=andreas+ding@gate450.dyndns.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).