When running sudo apt update in a debian template it uses sys-net.
Or in my case attempts to use it. I’m using a different vm for networking so it starts up sys-net instead. I’d rather this use my sys-vpn (which is connected to firewall > sys-net2) and is added as a netvm to the debian template
For some reason running this command starts a sys-net vm. This means sys-net can be made to run from within a different vm.
It also may mean that if I was allowing traffic through sys-net traffic can flow through this despite me not allowing it to do so.
Qubes vm update also fails with
Invalid response from proxy: HTTP/1.0 500 Unable to connect Server
I’ve also set mt dom0 update vm to use sys-vpn
Anyone know why this happens and is it a security risk?