Windows 10 Client Error Provisioning
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
On first startup while trying to provision the client I get through:
Login, Passphrase OK
Set a public name for this device:
There was an error provisioning
Unknown error: Error: rename
c:..\Roaming\Keybase\secretkeys. ..
c:..\Roaming\Keybase\secretkeys.[username].mapck: Access denied
I am executing the Client with elevated privileges.
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 first-startup provisioning on Windows 10 and capture the rename failure involving the Keybase secretkeys path and “Access denied.” No files or tests are named, so identify the provisioning entry point and determine what successful handling of this error should look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100