keybase / keybase/keybase-issues
keybase-installer: warn: No code-signing key (code@keybase.io) in GPG keychain #191
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Getting the following warning on doing a keybase-installer command :-
warn: No code-signing key (code@keybase.io) in GPG keychain
```
C:\Users\Aaron>keybase-installer
info: Made temporary directory: C:\Users\Aaron\AppData\Local\Temp\keybase_instal
l_-PmnY7RvQQbI_OTryFE_oA
info: Creating permanent keyring dir: C:\Users\Aaron\AppData\Roaming\.keybase-in
staller\keyring
warn: No code-signing key (code@keybase.io) in GPG keychain
info: Fetching URL https://dist.keybase.io/sig/files/1/keyset.json
info: Installing keyset version 1
info: Using keyset version v1
info: Fetching URL https://dist.keybase.io/sig/files/1/index.asc
info: Fetching URL https://dist.keybase.io/pkg/stable
Download /pkg/files/keybase-0.7.7.tgz [=========================================
========] 100% 0.0s (3597681 bytes total)
info: Fetching URL https://dist.keybase.io/sig/files/1/keybase-0.7.7.tgz.asc
info: verified signature of keybase-0.7.7.tgz against keybase-0.7.7.tgz.asc
info: Running npm install keybase-0.7.7.tgz: this may take a minute, please be p
atient
=====================================================================
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the keybase-installer command on the reported Windows setup and trace the source of the “No code-signing key (code@keybase.io) in GPG keychain” warning. Compare it with the later successful signature verification, then define done as either removing the incorrect warning or documenting why it is expected.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100