Page MenuHome GnuPG
Create Task
Maniphest T1688

IPSwitch/MoveIT PGP Public Key Import fail
Closed, ResolvedPublic
Actions

Description

When importing a PGP Public Key generated by IPSwitch's MoveIT Windows product
I receive the following: what "algo" is 3 or 2?

gpg2 -vvvvvv --import EnMoveITPROD.asc

gpg: using character set `utf-8'

gpg: armor: BEGIN PGP PUBLIC KEY BLOCK

Version: MOVEit Central 7.2.0.0

gpg: armor header:

Comment: http://www.ipswitchft.com

:public key packet:

version 4, algo 3, created 1312894460, expires 0

unknown algorithm 3

gpg: armor header:

gpg: can't handle public key algorithm 3

:user ID packet: "EnMoveITPROD <dmzadmin@en.com>"

:signature packet: algo 3, keyid AB991D5EB20C4F94

version 4, created 1312894460, md5len 0, sigclass 0x10

digest algo 8, begin of digest 5c 57

hashed subpkt 2 len 4 (sig created 2011-08-09)

hashed subpkt 9 len 4 (key expires after 10y0d0h0m)

subpkt 16 len 8 (issuer key ID AB991D5EB20C4F94)

unknown algorithm 3

:public sub key packet:

version 4, algo 2, created 1312894460, expires 0

unknown algorithm 2

gpg: can't handle public key algorithm 2

:signature packet: algo 3, keyid AB991D5EB20C4F94

version 4, created 1312894460, md5len 0, sigclass 0x18

digest algo 8, begin of digest 58 cb

hashed subpkt 2 len 4 (sig created 2011-08-09)

hashed subpkt 9 len 4 (key expires after 10y0d0h0m)

subpkt 16 len 8 (issuer key ID AB991D5EB20C4F94)

unknown algorithm 3

gpg: pub 0s/B20C4F94 2011-08-09 EnMoveITPROD <dmzadmin@en.com>

gpg: key B20C4F94: invalid self-signature on user ID "EnMoveITPROD
<dmzadmin@en.com>"

gpg: key B20C4F94: invalid subkey binding

gpg: key B20C4F94: skipped user ID "EnMoveITPROD <dmzadmin@en.com>"

gpg: key B20C4F94: skipped subkey

gpg: key B20C4F94: no valid user IDs

gpg: this may be caused by a missing self-signature

gpg: Total number processed: 1

gpg: w/o user IDs: 1

Details

Version
2.0.14

Event Timeline

Dione added projects: gnupg, Bug Report.Aug 15 2014, 6:58 PM
Dione set Version to 2.0.14.
Dione added a subscriber: Dione.
• werner added a subscriber: • werner.Aug 16 2014, 10:42 AM

2 and 3 are aliases for RSA. Some rarely used PGP versions used them to
indicate signing or encrypting RSA keys. GPG supports them. The specs say

   There are algorithm types for RSA Sign-Only, and RSA Encrypt-Only
   keys.  These types are deprecated.  The "key flags" subpacket in a
   signature is a much better way to express the same idea, and
   generalizes it to all algorithms.  An implementation SHOULD NOT
   create such a key, but MAY interpret it.

What version of libgcrypt are you using? ("gpg --version" shows that)

• werner lowered the priority of this task from High to Normal.Aug 16 2014, 10:42 AM
• werner added a comment.Aug 18 2014, 9:25 PM

Reply by email remarked that the vendor suggested to install gpg and use that to
create keys. Thus it seems to be a problem of MoveIT. Reporter asked to close
the bug.

• werner closed this task as Resolved.Aug 18 2014, 9:25 PM
• werner claimed this task.
• werner added a project: Not A Bug.