From: Marcus Frings <iam-est-hora-surgere@despammed.com>
Subject: Re: PGG broken?
Date: Tue, 23 May 2006 23:25:12 +0200 [thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86zmh8l9hj.fsf@shodan.gothgoose.net> (raw)
In-Reply-To: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86fyj5oc7m.fsf@shodan.gothgoose.net>
* 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.
> 2) Certain mails fail to decrypt. I'm asked for my passphrase again and
> again (and I *really* typed it correctly). Going back to an official
> Gnus release helped to successfully decrypt this certain mail.
> 3) I use PGG's passphrase-caching. I want to read an encrypted mail and
> enter my passphrase and the mail gets decrypted. Then I go to another
> encrypted mail and instead of decrypting it, I get:
Hm, does really nobody have an idea?
Regards,
Marcus
--
"The sun shines on the aluminium
I guess this must be the home of the hitmen"
next prev parent reply other threads:[~2006-05-23 21:25 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 ` Marcus Frings [this message]
2006-05-24 16:10 ` PGG broken? Norman Walsh
2006-06-02 3:44 ` Andreas Seltenreich
2006-06-04 4:38 ` Andreas Seltenreich
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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-86zmh8l9hj.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).