keybase / keybase/keybase-issues

pgp select fails on first usage

Open
#1,909 11 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

After signing up and logging in, I went to add my existing PGP key, but after unlocking the key I get an error:

```
$ keybase pgp select
# Algo Key Id Created UserId
= ==== ====== ======= ======
1 4096R 2B9F43E25E63BC17 Andrew Nicholson
Choose a key: 1
Collecting your passphrase for Import of key into keybase keyring.
▶ INFO Bundle unlocked: 2B9F43E25E63BC17
▶ ERROR key generation error: k.ToLksSKB() error: SecretSyncer: no device found for ID = ebb51a8698583b57190680230a963c18
```

Client: keybase version 1.0.5-0

GPG version info:

```
gpg (GnuPG/MacGPG2) 2.0.28
libgcrypt 1.6.3
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA, RSA, ELG, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `keybase pgp select` with an existing key using the reported client and GnuPG versions. Trace the `SecretSyncer: no device found` error and the key-import path; done means first-use PGP selection completes without the missing-device failure.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.