Issue:
Once there is component_whonix-host there would be two ACW popups. Once on Whonix-Host to configure Tor on the host and yet another one, fully independent in Whonix-Gateway doing the same.
My reasoning is that users who need to bridges or configure a proxy are likely to know. Or if they don’t know, they will know by trying to a direct connection and see it fails.
It is impossible to Hide Tor use from the internet service provider (ISP). It has been concluded this goal is difficult beyond practicality.
Our current implementation is flawed since forever anyhow:
Tor will make still certain network-related calls (like DNS lookups) even if DisableNetwork is set. Quote Tor man page (underline added):
DisableNetwork 0|1 When this option is set, we don’t listen for or accept any connections other than controller connections, and we close (and don’t reattempt) any outbound connections. Controllers sometimes use this option to avoid using the network until Tor is fully configured. Tor will make still certain network-related calls (like DNS lookups) as a part of its configuration process, even if DisableNetwork is set.
Removing the “Tor disabled by default” would allow to simplify Whonix source code.
