From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: PGP signature and ml software (was: Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg')
Date: Fri, 05 Aug 2005 14:05:54 +0200 [thread overview]
Message-ID: <9ehde4twpp.fsf_-_@gowron.rz-berlin.mpg.de> (raw)
In-Reply-To: <9ek6j0vcl0.fsf-G2iyDNEOhahHYNAXZw2rCoRsZ6cCL1yJ@public.gmane.org> (Jochen =?iso-8859-1?Q?K=FCpper's?= message of "Fri, 05 Aug 2005 13:37:47 +0200")
Jochen Küpper <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org> writes:
> Although I don't know whether this is relevant: I cannot verify the
> signature!
Ok, I see. Seems to be the old problem with the ml software not being
able to pass a PGP signature...
Greetings,
Jochen
--
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D
(Part 3 you find in my messages before fall 2003.)
next prev parent reply other threads:[~2005-08-05 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 15:02 Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg' field (was: Broken GPG signatures due to bad 'micalg' value) Reiner Steib
2005-07-29 6:33 ` Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg' field Daiki Ueno
2005-08-03 20:41 ` Simon Josefsson
2005-08-05 9:13 ` Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg' Daiki Ueno
[not found] ` <82e593ac-30c0-438c-b353-0f053f0ea2d0-7dooEoSoPCYjbB9gy5Vrp2D2FQJk+8+b@public.gmane.org>
2005-08-05 11:37 ` Jochen Küpper
[not found] ` <9ek6j0vcl0.fsf-G2iyDNEOhahHYNAXZw2rCoRsZ6cCL1yJ@public.gmane.org>
2005-08-05 12:05 ` Jochen Küpper [this message]
2005-08-05 12:55 ` Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg' field Simon Josefsson
2005-08-05 13:42 ` Reiner Steib
2005-08-08 11:16 ` 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=9ehde4twpp.fsf_-_@gowron.rz-berlin.mpg.de \
--to=jochen-+it19tn3rl9sbm7dsapr3bnah6klmebb@public.gmane.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).