SSL Woes? Device prorvisioning failed because this device went offline.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
On my Mac, when I launch the Keybase app for the first time and put in my username, I'm given the following message:
There was an error provisioning
Device provisioning failed because this device went offline.
Please check your network connection and try again.
This is almost certainly due to our company gateway swapping out keybase.io's SSL certificate to be one that is trusted our machines (because the company put it there), but not the Keybase software. I found an exchange where a cert was added to the tool with keybase config set proxy_ca_certs <pemfile> ... and I imagine something like this should work for me, but I'm still working at it.
Is there a way to simply disable cert-based authentication entirely? I can't seem to find the option, if one exists. If that is an easy fix and it does solve the problem, what would be the security implications?
Thank you, Keybase & co!
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
No source file or test is identified; start with the first-launch device provisioning path and the proxy_ca_certs configuration referenced in issue 3143. Determine whether corporate certificate interception is supported and document the security implications of any proposed authentication change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100