Well, I know why deleting the lines helped - because the many "verbose" lines changed the behavior of gpg. It made gpg send output that is supposed to be on stdout to stderr.
But I cannot tell you why the lines were there. Enigmail does not add any lines to gpg.conf.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I've got a similar problem. Before reinstalling my operating system I exported public and private key and now I can't import them as there's a problem with public key. How can I solve that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think I've got a similar problem. Before reinstalling my operating
system I exported public and private key and now I can't import them as
there's a problem with public key. How can I solve that?
The private key contains a copy of the public key -- just import the
private key and you should get both. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks. The problem is I've got only one file with my keys. It is supposed to contain both private and public, but import doesn't work. And now I don't know if there is a way to save the situation except to revoking old key and creating new one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To answer your original question "Is it recommended to use nightly builds instead of distribution specific versions?" - No, it's not recommended at all. Nightly builds represent the current development status and may contain bugs and uncompleted features.
Now that your keys are imported, I recommend you switch back to the release-version of Enigmail. I will release a new version of Enigmail that will fix the key importing issues soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To answer your original question "Is it recommended to use nightly builds instead of distribution specific versions?" - No, it's not recommended at all. Nightly builds represent the current development status and may contain bugs and uncompleted features.
Now that your keys are imported, I recommend you switch back to the release-version of Enigmail. I will release a new version of Enigmail that will fix the key importing issues soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I faced the same problems when trying to import someone elses public key: "Error - The first OpenPGP-Block is not a public key block".
I checked for "verbose" in gpg.conf - nothing in.
I installed nightly build - error message still there.
Many thanks for any further ideas how to solve.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, this is no public key. It's a message, encrypted for key 9316D00B12E1F9ED. No wonder you cannot import it as a key. You can try to decrypt it, if 9316D00B12E1F9ED is the id of your key pair. You can do that either on the command line:
gpg --decrypt publickey.pgp
Alternatively you can open it in a text editor, add an empty line on the top, save it, and open it in Thunderbird (File -> Open -> Saved message).
Last edit: Ludwig Hügelschäfer 2017-04-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, thanks. Maybe I misunderstood the sender of this file.
He mentioned that this is the PGP Certificate of his central mailadress to be used to send encrypted mails.
How do I have to handle this certificate?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The file is no certificate, at least not visible from the outside. As a side note: Please be aware that in OpenPGP language "key" is most times not only a key, but almost always a certificate. This is improper wording, but for historical reasons everyone used this.
The file is encrypted, and only the owner of the key with the id 9316D00B12E1F9ED can decrypt it. I just checked, that 9316D00B12E1F9ED is the encryption subkey of your main key.
So please, go ahead and try to decrypt it. It may contain your correspondants public key, maybe something else, but only you can see the content after decryption. Good luck!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I know why deleting the lines helped - because the many "verbose" lines changed the behavior of gpg. It made gpg send output that is supposed to be on stdout to stderr.
But I cannot tell you why the lines were there. Enigmail does not add any lines to gpg.conf.
So, since the output didn't go to stdout, Enigmail didn't realize the public key as legit, because it reads gpg's stdout for input?
Only the output of gpg --list-packets didn't go to stdout. But parsing of the list of packets expects the output on stdout, and nowhere else.
I see, thanks for the explanation and thanks everyone for your patience and your help!
I think I've got a similar problem. Before reinstalling my operating system I exported public and private key and now I can't import them as there's a problem with public key. How can I solve that?
The private key contains a copy of the public key -- just import the
private key and you should get both. :)
Thanks. The problem is I've got only one file with my keys. It is supposed to contain both private and public, but import doesn't work. And now I don't know if there is a way to save the situation except to revoking old key and creating new one.
Please try the latest nightly Enigmail build from
https://www.enigmail.net/index.php/en/download/nightly-build
OK, I was able to import, however now I'm unable to sign/encrypt messages...
Last edit: Włodzimierz Ziółkowski 2016-11-04
I try to import using wizard and using 'regular' way to import keys and both are unsuccessful.
Last edit: Włodzimierz Ziółkowski 2016-11-04
To answer your original question "Is it recommended to use nightly builds instead of distribution specific versions?" - No, it's not recommended at all. Nightly builds represent the current development status and may contain bugs and uncompleted features.
Now that your keys are imported, I recommend you switch back to the release-version of Enigmail. I will release a new version of Enigmail that will fix the key importing issues soon.
To answer your original question "Is it recommended to use nightly builds instead of distribution specific versions?" - No, it's not recommended at all. Nightly builds represent the current development status and may contain bugs and uncompleted features.
Now that your keys are imported, I recommend you switch back to the release-version of Enigmail. I will release a new version of Enigmail that will fix the key importing issues soon.
Thanks, that finally helped! I'm so glad! :)
Hello, I faced the same problems when trying to import someone elses public key: "Error - The first OpenPGP-Block is not a public key block".
I checked for "verbose" in gpg.conf - nothing in.
I installed nightly build - error message still there.
Many thanks for any further ideas how to solve.
If there are no privacy concerns, could you please send me the public key? (ludwig at enigmail dot net)
Thanks for fast response. Pls find attched the public key.
Well, this is no public key. It's a message, encrypted for key 9316D00B12E1F9ED. No wonder you cannot import it as a key. You can try to decrypt it, if 9316D00B12E1F9ED is the id of your key pair. You can do that either on the command line:
Alternatively you can open it in a text editor, add an empty line on the top, save it, and open it in Thunderbird (File -> Open -> Saved message).
Last edit: Ludwig Hügelschäfer 2017-04-14
Ok, thanks. Maybe I misunderstood the sender of this file.
He mentioned that this is the PGP Certificate of his central mailadress to be used to send encrypted mails.
How do I have to handle this certificate?
The file is no certificate, at least not visible from the outside. As a side note: Please be aware that in OpenPGP language "key" is most times not only a key, but almost always a certificate. This is improper wording, but for historical reasons everyone used this.
The file is encrypted, and only the owner of the key with the id 9316D00B12E1F9ED can decrypt it. I just checked, that 9316D00B12E1F9ED is the encryption subkey of your main key.
So please, go ahead and try to decrypt it. It may contain your correspondants public key, maybe something else, but only you can see the content after decryption. Good luck!
Got it - It was an encrypted key in an already encrypted mail!
Great support even on a public holiday, thanks a lot.
Thumbs up.
You're welcome :-) I just removed the attachment, it's of no use anymore being online.