No luck with Keybase...
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I can sort of login, but than I don't see a window for the UI and I can't open a new window. I do see a menubar. On the command line, I can login, but then it encounters an error after I give the device a name....
my log id: 8ac5010db57ba62ad0e4c11c
(1) Keybase can use GPG commands to sign the installation.
(2) Keybase can export your secret key from GPG and save it to keybase's local encrypted
keyring. This way, it can be used in 'keybase pgp sign' and 'keybase pgp decrypt'
going forward.
Which do you prefer?: 2
************************************************************
* Name your new device! *
************************************************************
Enter a public name for this device: IsleOfSkye
▶ ERROR bad signature: Can't find a key for *************: No keys match the given key IDs (code 1002)```Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Keybase desktop login and the command-line device naming flow described in the report, using log ID 8ac5010db57ba62ad0e4c11c. Investigate the missing UI window and the bad-signature error after choosing GPG option 2; done means login completes, a window can be opened, and device naming no longer fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100