Bad news yes. But well, nobody's dead. It's even quite funny in fact, thinking about how often I repeat to everybody that they need to make backup of everything.
This key is the only thing I loose, I will juste made another one. And no, I don't have the revocation certificate :( But I think it's not too bad, because nobody had access to this private key. I just loose it... Small and last question, If I make a new key, with the same email inside, will I be able to send it on servers ? (because they already got the old one...) Thanks a lot for your time. > > I'm afraid these are not the same key :( > > The former key is a 4096-bit RSA key. The latter key is a 1024-bit DSA > key with a 4096-bit ElGamal subkey bound to it. > > Also, the former key has an X.509 certificate assoiated with it, while > the latter keys are bound to your identity via OpenPGP certification. > While it's possible to have both X.509 certificates and OpenPGP > certificates from the same key (we're doing it for TLS servers in the > monkeysphere project), it's not common. And in your case, it's not what > you've done anyway, since these are clearly different keys because of > their different keylengths and algorithms. > > If you have no way of recovering your old ~/.gnupg/secring.gpg, you have > most likely lost control of your old key. In that case, i recommend > publishing the revocation certificate you created when you made your key > (hoping that you have such an old revocation certificate for 1F03B55A > stored someplace accessible to you). > > Sorry to be the bearer of bad news, > > --dkg > _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
