login – incompatible with loopback-pinentry
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I use pinentry-mode loopback in my gnupg.conf, so that I'd get the simple "Enter passphrase:" prompt instead of a popup window, and this seems to be incompatible with keybase:
Choose a key: 1
(a few seconds pass)
▶ ERROR GPG error: exit status 2
Maybe --pinentry-mode default should be added, or the loopback mode documented as not supported?
Arch Linux aur/keybase-release 4428.3e4cfb2-1
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 login failure with pinentry-mode loopback enabled in gnupg.conf and compare it with the default pinentry mode. Trace the login path that reports “GPG error: exit status 2”; the issue is complete when loopback mode either works or its unsupported status is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100