How to fix the user ID on an old (secret) key?

[Oskar L.]

johnmoore3rd at joimail.com wrote:

> Well, my first "attempt to repair" would be to "open" the Key with the
> Edit function in GPGshell and re-set the prefs (even if you keep them
> the same) and then use the "save" Command.  Whenever one "tinkers" with
> their Key a new self-signature is generated showing the date the "edit"
> was performed.

That does not help, because it only modifies the public key, and it's the
secret key that's causing this message. Here's the output for the secret
key from pgpdump again, can anyone tell me what's causing the "no valid
user IDs" message? Is there any way to remove the self-signature from the
secret key, and add a new one?

Oskar

Old: Secret Key Packet(tag 5)(481 bytes)
        Ver 4 - new
        Public key creation time - Fri Oct  3 06:58:46 EDT 2003
        Pub alg - DSA Digital Signature Algorithm(pub 17)
        DSA p(1024 bits) - ...
        DSA q(160 bits) - ...
        DSA g(1022 bits) - ...
        DSA y(1024 bits) - ...
        Sym alg - CAST5(sym 3)
        Iterated and salted string-to-key(s2k 3):
                Hash alg - SHA1(hash 2)
                Salt - 3f ac 9a 6c 32 e5 a5 94
                Count - 65536(coded count 96)
        IV - 75 29 8e f0 54 0b 20 5e
        Encrypted DSA x
        Encrypted SHA1 hash
Old: User ID Packet(tag 13)(43 bytes)
        User ID - anon0106 at yahoo.co.uk <anon0106 at yahoo.co.uk>
Old: Secret Subkey Packet(tag 7)(610 bytes)
        Ver 4 - new
        Public key creation time - Fri Oct  3 06:58:46 EDT 2003
        Pub alg - ElGamal Encrypt-Only(pub 16)
        ElGamal p(2048 bits) - ...
        ElGamal g(2 bits) - ...
        ElGamal y(2046 bits) - ...
        Sym alg - CAST5(sym 3)
        Iterated and salted string-to-key(s2k 3):
                Hash alg - SHA1(hash 2)
                Salt - 3f ac 9a 6c 32 e5 a5 94
                Count - 65536(coded count 96)
        IV - 3e 3c 75 2d 2e 2b 86 04
        Encrypted ElGamal x
        Encrypted SHA1 hash