GPG private key still does not work with PGP

Robert Allerstorfer Robert Allerstorfer <roal@anet.at>
Sun May 5 01:55:02 2002


Hi,

unfortunately, the final version 1.0.7 still has the same problem as
1.0.6c had, as I have posted at

http://marc.theaimsgroup.com/?l=gnupg-devel&m=100936896100459&w=2

but nobody mentioned anything about it.

In short: If you generate a DSA and ElGamal keypair and export the
public and private key in ASCII, the private key cannot be exported by
PGP 6.5.8 (the public can, though). The PGP error message is "The
keyring file is corrupt".

Here is the log of the key creation:

[roal@ns roal]$ ./gpg --gen-key
gpg: Warning: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: keyring `/home/roal/.gnupg/secring.gpg' created
gpg: keyring `/home/roal/.gnupg/pubring.gpg' created
Please select what kind of key you want:
   (1) DSA and ElGamal (default)
   (2) DSA (sign only)
   (4) ElGamal (sign and encrypt)
   (5) RSA (sign only)
Your selection? 1
DSA keypair will have 1024 bits.
About to generate a new ELG-E keypair.
              minimum keysize is  768 bits
              default keysize is 1024 bits
    highest suggested keysize is 2048 bits
What keysize do you want? (1024) 2048
Requested keysize is 2048 bits       
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Key is valid for? (0) 
Key does not expire at all
Is this correct (y/n)? y
                        
You need a User-ID to identify your key; the software constructs the user id
from Real Name, Comment and Email Address in this form:
    "Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>"

Real name: ANET - New Media Solutions
Email address: info@anet.at          
Comment:                   
You selected this USER-ID:
    "ANET - New Media Solutions <info@anet.at>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
You need a Passphrase to protect your secret key.    

We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
++++++++++++++++++++++++++++++++++++++++.+++++++++++++++.+++++++++++++++.++++++++++...+++++.+++++++++++++++.++++++++++++++++++++.+++++..+++++>++++++++++...............................................................................................................................................+++++
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
.+++++..++++++++++.++++++++++++++++++++.+++++.+++++.++++++++++++++++++++..+++++.++++++++++.+++++.+++++...+++++.+++++++++++++++++++++++++.++++++++++.+++++.++++++++++>.++++++++++>+++++>+++++.............................+++++^^^
gpg: /home/roal/.gnupg/trustdb.gpg: trustdb created
public and secret key created and signed.
key marked as ultimately trusted.

pub  1024D/C3DDD1B6 2002-05-04 ANET - New Media Solutions <info@anet.at>
     Key fingerprint = 3106 C835 C96C F5E7 A2B9  9413 0C6B 2F13 C3DD D1B6
sub  2048g/FA575882 2002-05-04


[roal@ns roal]$ ./gpg --export-secret-keys -a -o sec.asc
gpg: Warning: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Warning: unsafe permissions on file "/home/roal/.gnupg/pubring.gpg"
[roal@ns roal]$ ./gpg --export -a -o pub.asc
gpg: Warning: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: Warning: unsafe permissions on file "/home/roal/.gnupg/pubring.gpg"


Hope that someone now takes care of this bug.


--
rob.