Play with Cloudflare Zero Touch
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- Comment out all DNS settings in
/etc/systemd/resolved.conf, as told in Cloudflare Zero Touch FAQ's "WARP on Linux shows DNS connectivity check failed".curl -s https://www.cloudflare.com/cdn-cgi/trace | grep -i 'warp='show 'warp=plus'. - Add Cloudflare's root CA to OS, GitHub, Python and NPM. The files are specified here
/etc/pki/ca-trust/source/anchors. - Use split tunnelling Include mode so
gateway=offis the right behavior, as specified in this post.
TODO:
- Confirm that LibreWolf Flatpak has imported the root CA.
- VSCodium Flatpak hasn't been able to import the root CA files so
gitinside VSCodium Flatpak can use it , despite setting the permissions. - GitHub Copilot Chat sometimes can't connect, might be resolved if the above problem is resolved as well.
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 /etc/systemd/resolved.conf and the Cloudflare trace command to verify the current WARP and DNS behavior. Then review /etc/pki/ca-trust/source/anchors and the TODO items for LibreWolf and VSCodium Flatpaks. Done means the root CA works across the listed clients and the remaining connectivity checks are confirmed or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, linux, python
- Domain
- devops, security, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100