Windows device provision using GPG fails
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I am attempting to provision a new Windows device using the account's GPG key. The GPG installed on my machine is from Git for Windows. The Keybase client fails to provision the device, stating that GPG exited with error code 2.
The log files (keybase.service.log, line 548) show that the GPG command failed, with error message Sorry, no terminal at all requested - can't get input. The command is C:\Program Files\Git\usr\bin\gpg.exe --no-tty --armor --sign -u 71512e5884b9ca120acec8de3f6bcec7d3e099af.
If additional logs or information would be helpful, I can provide them.
my log id: f1494a490d0770d16bfa321c
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 with keybase.service.log at line 548 and the reported GPG command using Git for Windows. Reproduce Windows device provisioning with the account GPG key, then trace the failure associated with error code 2 and the no-terminal message. Done means provisioning completes successfully with this GPG setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100