I created a key pair from the stand alone PGP program, the Symantec Desktop Encryption 10.3.2, where I usually create all my keys - tried to import it into Enigmail Thunderbird and the public key successfully imported but it denied the secret key import and got a message that it is probably a GNU bug. Now I can import it successfully IF I import the entire secret key ring (skr) but I don't need to import all my keys which I did previously and don't want to have to do all that again. I just want to import a new secret key pair. What is keeping it from being imported? I created one also for someone else on the stand alone pgp desktop program for their use for a different program so I also work with others who uses keys with other programs. I tried making one for another Tbird/enigmail user and they could not import it either. How can this be solved? I'm using the latest version of tbird, enigmail and gnu programs. All help that solves this is appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First of all, if not done already, I'd upgrade to the latest version of GnuPG and retry. If it doesn't work using Enigmail, then you might try the command line:
gpg--importsecretkeys.file
If it still doesn't work, then there is a problem with GnuPG, which you would need to report to the GnuPG developers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok. I'm confused about the gpg command line. How do I do that?
On 3/5/2019 2:12 AM, Patrick Brunschwig wrote:
First of all, if not done already, I'd upgrade to the latest version of
GnuPG and retry. If it doesn't work using Enigmail, then you might try
the command line:
gpg --import secretkeys.file
If it still doesn't work, then there is a problem with GnuPG, which you
would need to report to the GnuPG developers.
I found out how to try it. I tried that and it says there is no such
file. The name of the file is Charles Rollins.asc so the command I put
was exactly what you put and in place of "secretkeys.file I put charles
rollins.asc which is the secret/public key file and it says there was no
such file and I had it right there in the correct folder.
On 3/5/2019 4:18 PM, Charles wrote:
Ok. I'm confused about the gpg command line. How do I do that?
On 3/5/2019 2:12 AM, Patrick Brunschwig wrote:
Firstofall,ifnotdonealready,I'd upgrade to the latest version ofGnuPGandretry.Ifitdoesn't work using Enigmail, then you might trythecommandline:gpg--importsecretkeys.fileIfitstilldoesn't work, then there is a problem with GnuPG, which youwouldneedtoreporttotheGnuPGdevelopers.------------------------------------------------------------------------Importspublickeybutdeniessecretkeyhttps://sourceforge.net/p/enigmail/forum/support/thread/6ee3fcddee/?limit=25#c175------------------------------------------------------------------------Sentfromsourceforge.netbecauseyouindicatedinterestinhttps://sourceforge.net/p/enigmail/forum/support/Tounsubscribefromfurthermessages,pleasevisithttps://sourceforge.net/auth/subscriptions/
Yes, this looks like GnuPG is refusing to import the key. There seems to be a key without any valid "User ID" field (that's the field containing your name / email address). Such keys don't comply to the OpenPGP standard, and I believe that therefore GnuPG won't import them.
I'm not sure what you can do about it. I think it's best if you ask for support at the GnuPG Users mailing list
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right. I have been communicating with them and the culprit is
PGP Desktop by Symantec. It produces a secret key that is out of the
normal structure and in their words "tears it up". So the makers of
GnuPG are going to try to improve upon it and maybe the next version
will be able to import it. I sent them a test.asc file and they created
one themselves and they could not even import their own test saying PGP
Desktop is tearing it up so we have to wait and see what their solution is.
On 3/7/2019 11:36 AM, Patrick Brunschwig wrote:
Yes, this looks like GnuPG is refusing to import the key. There seems to
be a key without any valid "User ID" field (that's the field containing
your name / email address). Such keys don't comply to the OpenPGP
standard, and I believe that therefore GnuPG won't import them.
I created a key pair from the stand alone PGP program, the Symantec Desktop Encryption 10.3.2, where I usually create all my keys - tried to import it into Enigmail Thunderbird and the public key successfully imported but it denied the secret key import and got a message that it is probably a GNU bug. Now I can import it successfully IF I import the entire secret key ring (skr) but I don't need to import all my keys which I did previously and don't want to have to do all that again. I just want to import a new secret key pair. What is keeping it from being imported? I created one also for someone else on the stand alone pgp desktop program for their use for a different program so I also work with others who uses keys with other programs. I tried making one for another Tbird/enigmail user and they could not import it either. How can this be solved? I'm using the latest version of tbird, enigmail and gnu programs. All help that solves this is appreciated.
First of all, if not done already, I'd upgrade to the latest version of GnuPG and retry. If it doesn't work using Enigmail, then you might try the command line:
If it still doesn't work, then there is a problem with GnuPG, which you would need to report to the GnuPG developers.
Ok. I'm confused about the gpg command line. How do I do that?
On 3/5/2019 2:12 AM, Patrick Brunschwig wrote:
--
John 14:6
I found out how to try it. I tried that and it says there is no such
file. The name of the file is Charles Rollins.asc so the command I put
was exactly what you put and in place of "secretkeys.file I put charles
rollins.asc which is the secret/public key file and it says there was no
such file and I had it right there in the correct folder.
On 3/5/2019 4:18 PM, Charles wrote:
--
John 14:6
It's probably best if you save the file with your key on the desktop.
Then you can import the file using:
Ok, here is the message I got back:
C:\Users\croll>gpg --import "Desktop\Charles Rollins.asc"
gpg: key C7EE3D25FF2E5EF5: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: key C7EE3D25FF2E5EF5: failed to re-lookup public key
gpg: key C7EE3D25FF2E5EF5: public key "Charles Rollins
crollinsphoto@gmail.com" imported
gpg: Total number processed: 2
gpg: w/o user IDs: 1
gpg: imported: 1
gpg: secret keys read: 1
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 4 signed: 9 trust: 0-, 0q, 0n, 0m, 0f, 4u
gpg: depth: 1 valid: 9 signed: 0 trust: 1-, 0q, 0n, 0m, 8f, 0u
gpg: next trustdb check due at 2019-11-05
Last edit: Patrick Brunschwig 2019-03-07
Yes, this looks like GnuPG is refusing to import the key. There seems to be a key without any valid "User ID" field (that's the field containing your name / email address). Such keys don't comply to the OpenPGP standard, and I believe that therefore GnuPG won't import them.
I'm not sure what you can do about it. I think it's best if you ask for support at the GnuPG Users mailing list
You are right. I have been communicating with them and the culprit is
PGP Desktop by Symantec. It produces a secret key that is out of the
normal structure and in their words "tears it up". So the makers of
GnuPG are going to try to improve upon it and maybe the next version
will be able to import it. I sent them a test.asc file and they created
one themselves and they could not even import their own test saying PGP
Desktop is tearing it up so we have to wait and see what their solution is.
On 3/7/2019 11:36 AM, Patrick Brunschwig wrote:
--
John 14:6