keybase / keybase/keybase-issues

Cannot add new PGP key via curl after revoked an old key

Open
#2,310 24 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Short steps

  1. Click add a PGP key on webpage
  2. Paste my pubkey on the dialog
  3. Execute command from dialog
  4. curl finally says: curl: (52) Empty reply from server

Then I refreshed the webpage, no PGP key was shown on my page.

Also tried keybase id frantic1048 , I get ▶ ERROR (error 901) .

Then I repeated again above operation, at the curl step, I get

Error in your post
-------------------

Code: 908
Name: KEY_NEED_REVOKE
Description: You need to delete your active key before uploading a new one

It looks like my key is uploaded. But I can't find my key via webpage or keybase id

Long story

You can follow this log for extra information: https://keybase.io/frantic1048/sigchain

  • I registered keybase.
  • Login with CLI version of keybase
  • Generated a device key, and paper key
  • Added PGP key with with CLI version of keybase
  • added some proofs

So far, everything looks good.

Then I found device key is a little superfluous for me, I want to manage my key like this -> https://keybase.io/alexmartin/graph .

  • I keybase deprovision my device.
  • The webpage still shows my PGP key, but with red ooops text beside it.
  • I click that text, it says I need to re-verify my pubkey
  • I follow the instruction, paste curl command from webpage to terminal

curl gets:

Error in your post
-------------------

Code: 908
Name: KEY_NEED_REVOKE
Description: You need to delete your active key before uploading a new one

I've no idea why this happened. Then I revoked my old key, tried to add the new key. But I found I cannot add my new key as above Short steps described.

my keybase profile : https://keybase.io/frantic1048/
my log id: 099b2bfbabd736f18cb4321c

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the webpage's curl flow after revoking the old key, then compare the reported 901 and 908 responses with the linked sigchain and profile. Done means a replacement PGP key can be uploaded after revocation and is visible on the webpage and through keybase id.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.