Encrypted public key should be decrypted and properly imported.
Reported by Brennan Novak | May 26th, 2014 @ 07:39 PM | in 1.2b1 (closed)
Hello. I recently tried to import a key that was sent to me. I've attached it for your purposes. The importing via GPG Keychain presented the following error:
` Import failed!
Code = 0
Error text:
gpg: [don't know]: invalid packet (ctb=3c)
gpg: read_block: read error: Invalid packet
gpg: import from /dev/fd/5' failed: Invalid keyring gpg:
Total number processed: 0
But upon running `gpg --decrypt 0x29E45AE0.asc.pgp from the CLI I was successfully able to decrypt it and import the key into GPG Keychain!
Comments and changes to this ticket
-
Luke Le May 26th, 2014 @ 07:44 PM
- Importance changed from “” to “Low”
Hi Brennan,
the key you've attached is encrypted to you. If your plan was to encrypt it to us as well, it seems like you didn't use the our proper public key (unfortunately a few fake ones/mistakenly created ones are on the key server).
If however you didn't know that the attached key was encrypted, you have to first decrypt it, using gpg services or command line and only after import it into GPG Keychain Access. -
Brennan Novak May 26th, 2014 @ 08:08 PM
Hey Luke. Thanks for the response and feedback. Yes, that seems to be the scenario- the sender encrypted the key to me. I was able to decrypt it via the CL because I do have the private key which it was encrypted to. Shouldn't GPG Keychain have been able to decrypt it instead of erroring out?
-
Luke Le May 26th, 2014 @ 08:29 PM
- Title changed from “GPG Tools fails on importing ASCII-armored keys” to “Encrypted public key should be decrypted and properly imported.”
Hi Brennan,
indeed it should. GPG Keychain Access is not content aware at the moment, but even if we'll not see this case often and haven't seen it before, it would certainly make sense for GKA to handle this case properly.
I'll change the title so this becomes a feature request.
-
-
Mento July 10th, 2014 @ 06:23 AM
- State changed from “new” to “fixed”
- Assigned user set to “Mento”
- Milestone set to “1.2b1”
-
steve July 10th, 2014 @ 08:46 AM
- State changed from “fixed” to “verified”
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Brennan Novak
Luke Le
Mento
steve