Self-signed certificate used on api.keybase.io is blocked by some firewalls
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hi there,
It looks like the self-signed cert used on api.keybase.io is blocked by some firewalls. This apprears to be a consequence of the firewall's inability to fully validate the certificate chain (unknown Root CA). Whitelisting *.keybase.io on the firewall, or using a VPN connection fixes the problem. Note: This issue is related to #6004.
My log id: cfb0941f74341b83589dec1c
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 reviewing the certificate configuration for api.keybase.io and the related issue #6004, then reproduce the failure described for firewalls that cannot validate the chain. Use log id cfb0941f74341b83589dec1c as supporting context. Done means api.keybase.io is reachable through affected firewalls without requiring a whitelist or VPN.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100