KBFS timeouts when using 'disable-cert-pinning'
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I had to use the disable-cert-pinning option because the machine is behind an aggressive firewall which basically MITM-attacks all traffic. The GUI app seems to work, however as soon as I tried to cd more than two levels "deep" in a KBFS team folder, it started throwing "The read operation took too long and failed" errors over and over again.
Log ID: 700ae48f71c75cfd13c49e1c
Running 6.0.3-20221212202006+608e46df72 on macOS 13.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 with the reported Log ID 700ae48f71c75cfd13c49e1c and reproduce the repeated read failures while using disable-cert-pinning on macOS. Trace the KBFS team-folder traversal that fails beyond two levels, and consider the issue done when that traversal completes without timeout errors in the reported environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100