Qubes-Whonix™ Networking
Donate
Guide to networking inside Qubes Templates, including how to use commands like curl, gpt and git.
Introduction[edit]
Qubes Templates are non-networked by default. This is a security feature.
- Why are APT operating system upgrades functional? Qubes has a special implementation for that. APT isn't using networking in Qubes Templates but qrexec. Documented on the Qubes/UpdatesProxy wiki page.
- How to make other applications functional inside Qubes Templates such as
curl,gpg,git? This is documented below.
This is unspecific to Whonix. This is as per Qubes upstream design default. Whonix does not influence this.
HowTo: Networking inside Qubes Templates[edit]
Warning: Users are not supposed to do that. However, Advanced Users understanding 
Computer Security Threat Modeling
, that understand
Computer Security Mental Model
might sometimes do this.
Note: Replace command with the actual command. [1]
UWT_DEV_PASSTHROUGH=1 http_proxy=http://127.0.0.1:8082 https_proxy=http://127.0.0.1:8082 command
Forum Discussion[edit]
- Qubes forums: Curl-proxy / wget-proxy scripts in Templates so users can add GPG distro keys linked to added external repositories
Footnotes[edit]
- ↑
UWT_DEV_PASSTHROUGH=1is redundant but harmless in some cases.UWT_DEV_PASSTHROUGH=1is required in some cases to circumvent Whonix's default Stream Isolation wrappers. Otherwise, original.anondist-origbinaries would need to be used. http_proxy=http://127.0.0.1:8082 https_proxy=http://127.0.0.1:8082 curl.anondist-orig [...] http_proxy=http://127.0.0.1:8082 https_proxy=http://127.0.0.1:8082 git.anondist-orig [...]
The most watertight privacy operating system in the world.
At
Whonix we value freedom and trust, supporting Open Source and Freedom Software
2012-
2025 ENCRYPTED SUPPORT LLC
We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!