[Bug 1460782] Re: public key listing fails if ECC subkey uses SHA512

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnupg2 (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg2 in Ubuntu.
https://bugs.launchpad.net/bugs/1460782

Title:
  public key listing fails if ECC subkey uses SHA512

Status in gnupg2 package in Ubuntu:
  Confirmed
Status in gnupg2 package in Debian:
  Unknown

Bug description:
  Using Gnupg 2.0.22-3ubuntu1.3 (in UbuntuStudio 1404 LTS)

  With appearance of gnupg 2 Modern which is now at 2.1.4, increasing
  numbers of users are creating and using ECC keys or subkeys.  Of
  course 2.0.xx cannot handle these keys but in 2.0.22 if one of the
  keys in the pubring has a subkey which uses SHA512, then an attempt to
  list pubkeys with gpg2 -k fails to complete with the following error
  message :

  gpg: Ohhhh jeeee: can't encode a 512 bit MD into a 608 bits frame
  Aborted (core dumped)

  
  and returns error code 134 

  The presence of a single such key in the keyring also prevents
  enigmail displaying details of some keys.

  More details of the discussion are on the user thread of gnupg-users
  list started on 18 May 2015 under subject heading

  "Ohhhh jeeee: can't encode a 512 bit MD into a 608 bits frame"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1460782/+subscriptions