search

google / end-to-end

End-To-End is a crypto library to encrypt, decrypt, digital sign, and verify signed messages (implementing OpenPGP)
Apache License 2.0
4.13k stars 298 forks source link

Unable to reimport secret and public keys exported by end-to-end #174

Closed koto closed 9 years ago

koto commented 9 years ago

From vincent....@gmail.com on 2014-08-26 15:31:01

koto commented 9 years ago

From vincent....@gmail.com on 2014-08-26 15:31:01

koto commented 9 years ago

From koto@google.com on August 26, 2014 09:27:20

We generated invalid signatures at a certain point in history, but the signature verification was not implemented then. Now we verify the signatures, spotted that bug and fixed it in the trunk.

If signatures you generated are invalid, there are two ways we could go:

First though, let's make sure that the signatures are indeed invalid. Could you post your public key?

Status: Accepted
Owner: koto@google.com

koto commented 9 years ago

From vincent....@gmail.com on August 26, 2014 23:24:25

Thank you for these explanations. With gpg (and gpg2) I could import the secret key, but not the public one (see precedent transcript).

Here is the public key.

2014-08-26 18:27 GMT+02:00 end-to-end@googlecode.com:

koto commented 9 years ago

From koto@google.com on August 27, 2014 06:24:24

I did not get the key. Please export the public key e.g. from the extension options page by clicking save icon next to your email (it should begin with --BEGIN PGP PUBLIC KEY BLOCK--)

koto commented 9 years ago

From vincent....@gmail.com on August 27, 2014 10:14:24

I cannot export the key now because it was canceled when I uninstalled the extension. But I had made a backup of the keys. When I try now to import the backed up key it is impossible and I get the error explained above.

Here is the public key: -----BEGIN PGP PUBLIC KEY BLOCK----- Charset: UTF-8 xv8AAABSBAAAAAATCCqGSM49AwEHAgMEFiQCQawKLhyOvVYNk6hCXVmleSV3tvyd IFsZgzS4seSSM/FAVTth81I9LcqQWHQiAE4vrt2e3zINPV31JLpUb83/AAAAGzx2 aW5jZW50LmxhaXNuZXlAZ21haWwuY29tPsL/AAAAhgQQEwgAOP8AAAAFglPmMVj/ AAAAAosJ/wAAAAmQK4CCbmyUdRz/AAAABZUICQoL/wAAAAOWAQL/AAAAAp4BAABx DwEA0kk8mJJ3UBamb8jz7QhPmjMVhaOIUJ2pnfsrMEoj4bQA/02ZVJtJ/da2+9Xn bcmPukeA/2u4L2Cke7SfcFCCCo/Wzv8AAABWBAAAAAASCCqGSM49AwEHAgMEQVF8 I+JcJsaReh42iHvaBrahVNoY77NJUXWJJCWgBUYsbV/LRhEpyEgGuX7ReeW7NdJ8 QldU6/hg3YrHR/2JIgMBCAfC/wAAAGYEGBMIABj/AAAABYJT5jFY/wAAAAmQK4CC bmyUdRwAAFAwAP0X2P/OVuGYsGuUmxtawYV9Fo3VgURDYT21d9RIVeh3kwD9Hg7d EiHTR5DMWogx5j1dBRMwJy5Z1F9218LrmVEqFDc= =v1hr -----END PGP PUBLIC KEY BLOCK-----

Thank you very much for the help if it is an error in the import procedur of present version. But for my key, I can generate another, since I have not yet diffused it.

2014-08-27 15:24 GMT+02:00 end-to-end@googlecode.com:

koto commented 9 years ago

From koto@google.com on August 28, 2014 09:08:55

Yes, the key has invalid signatures. If you didn't use it much, just recreate the keypair. In the newest source code release the whole signature verification is already completed.

Status: Fixed

koto commented 9 years ago

From vincent....@gmail.com on August 29, 2014 09:16:10

Thank you very much!

2014-08-28 18:09 GMT+02:00 end-to-end@googlecode.com: