From: Simon Josefsson <jas@extundo.com>
Cc: Ding List <ding@gnus.org>,
Reiner Steib <reinersteib+gmane@imap.cc>,
Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de>
Subject: Re: Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg' field
Date: Wed, 03 Aug 2005 22:41:38 +0200 [thread overview]
Message-ID: <ilu64umn471.fsf@latte.josefsson.org> (raw)
In-Reply-To: <dcfedf2b-40aa-4522-9662-1efa7959c698@well-done.deisui.org> (Daiki Ueno's message of "Fri, 29 Jul 2005 15:33:35 +0900")
Daiki Ueno <ueno@unixuser.org> writes:
> I'm not sure that the micalg= parameter is still mandatory, while the
> hash algorithm used is embedded in OpenPGP packets.
Sadly RFC 1847 require the presence of micalg, it seems. A wart, but
difficult to fix at this point. We should populate it with correct
information.
> It can be obtained by using the builtin packet parser (pgg-parse),
> without depending on --status-fd output of GnuPG.
Very nice! Would you mind proposing a patch for mml2016.el that uses
this approach?
Thanks.
next prev parent reply other threads:[~2005-08-03 20:41 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 [this message]
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 ` PGP signature and ml software (was: Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg') Jochen Küpper
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=ilu64umn471.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
--cc=enrico.scholz@informatik.tu-chemnitz.de \
--cc=reinersteib+gmane@imap.cc \
/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).