Open sparxnet000 opened 4 years ago
Ok - so the solution was to first list the keys I had available with
keybase pgp list
Then I copied the keybase key ID and (NOT the PGP key ID or fingerprint) and used that value in
keybase pgp drop <keybase key-id>
The command help should clarify that in the absence of any help files/tutorials.
key-id = Keybase key ID and NOT GPG key ID
Ok - so the solution was to first list the keys I had available with
keybase pgp list
Then I copied the keybase key ID and (NOT the PGP key ID or fingerprint) and used that value in
keybase pgp drop <keybase key-id>
The command help should clarify that in the absence of any help files/tutorials.
key-id = Keybase key ID and NOT GPG key ID
Of course, that still doesn't explain why I couldn't initially drop via the Android app GUI...
I had previously uploaded my public key 0x7D618792A3E069DE to keybase.
This existing 2048 bit RSA key is expiring soon, so I decided to create a new ECC key. I uploaded the new key via the CLI using the
keybase pgp select --multi
command.I would like to remove the soon to be expiring key and first tried to drop it from the Android app. That didn't work - no error message or changes. Next, I tried using the command
keybase pgp drop 7D618792A3E069DE
from the CLI only to encounter the following message:Error parsing command line arguments: bad key: KID wrong length; wanted 35 but got 8 bytes
Am I using the syntax incorrectly or is there some other issue ?
Regards,
Shahrzaad Parekh https://keybase.io/sparx