keybase / keybase/keybase-issues

Cannot Update Key Edited Elsewhere.

Open
#2,256 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Hello,

Please forgive my ignorance if I'm doing something wrong.

I have an updated key (added several sub-keys) that I edited in GPGTools that I would like to update Keybase with.

However, whenever I try to update the key (using each of the 3 methods; WebUI, Keybase CLI, and cURL) I get an error returned that says "Error: failed to post to the server: bad base 64 string".

When I try to update with the Keybase CLI, it says the key is already up to date.
When I try to decrypt something that was encrypted with the new encrypting sub key, it says that the key can't be found to decrypt.
(The correct decryption key is in fact in my GPG Keyring because I am able to use GPGTools to decrypt the same message)

Is there any additional troubleshooting steps I can take or is this a bug?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the key update through the WebUI, Keybase CLI, and cURL paths using the externally edited GPG key, then inspect where the “bad base 64 string” error occurs. Done means the updated key, including its added sub-keys, is accepted and messages encrypted with the new encryption sub-key can be decrypted through Keybase.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.