[Gpg4win-devel] Key Import Error

Bernhard Reiter bernhard at intevation.de
Wed Sep 16 11:44:37 CEST 2009


Am Dienstag, 15. September 2009 16:58:47 schrieb daniel huber:
> Why is it not possible to import such a key into gpg4win/kleopatra? Is it
> because there is no self signature? Form me, there is no reason for an
> error, since such a key can be imported in every PGP-Plugin (from PGP-Corp)
> and also in the previous version 1.1.4 of GPG4WIN.
>
> -----BEGIN PGP PUBLIC KEY BLOCK-----
> Version: BCPG v1.33

I've tried this with gpg (GnuPG) 2.0.12 on GNU/Linux with options "-vvv":
:public key packet:
        version 4, algo 3, created 1253006399, expires 0
        unknown algorithm 3
gpg: armor header:
gpg: can't handle public key algorithm 3
user ID packet: " <daniel at mtx.mailtest.kko.ch>"
:signature packet: algo 1, keyid E5FC2496C9A5F71C
        version 4, created 1253006399, md5len 0, sigclass 0x13
        digest algo 2, begin of digest fb 94
        hashed subpkt 2 len 4 (sig created 2009-09-15)
        hashed subpkt 16 len 8 (issuer key ID E5FC2496C9A5F71C)
        data: [1018 bits]
:signature packet: algo 3, keyid 5A36A2A38D7B32E2
        version 4, created 1253006399, md5len 0, sigclass 0x13
        digest algo 2, begin of digest b7 a9
        hashed subpkt 2 len 4 (sig created 2009-09-15)
        hashed subpkt 16 len 8 (issuer key ID 5A36A2A38D7B32E2)
        hashed subpkt 0 len 1 (?)
        hashed subpkt 9 len 4 (key expires after 2y0d0h0m)
        unknown algorithm 3
:public sub key packet:
        version 4, algo 2, created 1253006399, expires 0
        unknown algorithm 2
gpg: can't handle public key algorithm 2
:signature packet: algo 3, keyid 5A36A2A38D7B32E2
        version 4, created 1253006399, md5len 0, sigclass 0x18
        digest algo 2, begin of digest b4 d2
        hashed subpkt 2 len 4 (sig created 2009-09-15)
        hashed subpkt 16 len 8 (issuer key ID 5A36A2A38D7B32E2)
        hashed subpkt 0 len 1 (?)
        hashed subpkt 9 len 4 (key expires after 2y0d0h0m)
        unknown algorithm 3
gpg: pub     0s/8D7B32E2 2009-09-15   <daniel at mtx.mailtest.kko.ch>
gpg: key 8D7B32E2: invalid self-signature on user ID " 
<daniel at mtx.mailtest.kko.ch>"
gpg: key 8D7B32E2: invalid subkey binding
gpg: key 8D7B32E2: skipped user ID " <daniel at mtx.mailtest.kko.ch>"
gpg: key 8D7B32E2: skipped subkey
gpg: key 8D7B32E2: no valid user IDs
gpg: this may be caused by a missing self-signature

It seems the version of gpg2 I am having here does not support
reading the following algorithms anymore:     
      2          - RSA Encrypt-Only [HAC]
      3          - RSA Sign-Only [HAC]
rfc4880 notes:
   Encrypt-Only (2) and RSA Sign-Only are deprecated and SHOULD NOT be
   generated, but may be interpreted.
and 
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

It seems that gpg 1 can still interpret them, I could import the key with it
on my system:
LANG=C gpg --version
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA

LANG=C gpg2 --version
Pubkey: RSA, ELG, DSA

Hmmm, I guess I need to ask this on gnupg-users@ or gnupg-devel.
Bernhard




-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.wald.intevation.org/pipermail/gpg4win-devel/attachments/20090916/69b3ed83/attachment.pgp


More information about the Gpg4win-devel mailing list