unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: bug-gnu-emacs@gnu.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	594510-forwarded@bugs.debian.org, 594510@bugs.debian.org
Subject: Bug#594510: emacs23-common: OpenPGP-signed message composition uses micalg=pgp-rmd160 instead of micalg=pgp-ripemd160
Date: Fri, 26 Nov 2010 13:58:18 -0600	[thread overview]
Message-ID: <87k4jz502t.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <20100826140802.24368.1346.reportbug@localhost.localdomain> (Daniel Kahn Gillmor's message of "Thu, 26 Aug 2010 10:08:02 -0400")

[If possible, please preserve 594510-forwarded@bugs.debian.org in any replies.]

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

>
> /usr/share/emacs/23.1/lisp/epg.elc lists OpenPGP's digest algorithms
> as follows:
>
> (defconst epg-digest-algorithm-alist #3#)) ((1 . "MD5") (2 . "SHA1")
> (3 . "RMD160") (8 . "SHA256") (9 . "SHA384") (10 . "SHA512"))
>
> but the declaration for RIPEMD160 is wrong, according to the registry
> in RFC 4880.  It should be:
>
> (defconst epg-digest-algorithm-alist #3#)) ((1 . "MD5") (2 . "SHA1")
> (3 . "RIPEMD160") (8 . "SHA256") (9 . "SHA384") (10 . "SHA512"))
>
> This causes messages to be produced with a mismatched pgp-micalg entry
> in the Content-Type: line, which in turn causes some MUAs to fail to
> validate them.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4




       reply	other threads:[~2010-11-26 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100826140802.24368.1346.reportbug@localhost.localdomain>
2010-11-26 19:58 ` Rob Browning [this message]
2010-12-03  1:56   ` bug#7490: Bug#594510: emacs23-common: OpenPGP-signed message composition uses micalg=pgp-rmd160 instead of micalg=pgp-ripemd160 Daiki Ueno
     [not found]   ` <m362vby5zj.fsf-ueno@unixuser.org>
2010-12-03 19:22     ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k4jz502t.fsf@raven.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=594510-forwarded@bugs.debian.org \
    --cc=594510@bugs.debian.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=dkg@fifthhorseman.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).