Hello, while upgrading to sys-whonix-14 many weeks ago, I was fighting to maintain my Fedora and Debian Template to keep using sys-net not sys-whonix-14
and sys-whonix-gw and -ws to use sys-whonix-14 , which are otherwise working fine and I hesitate to mess with /etc/qubes-rpc/policy/qubes.UpdatesProxy However, once in a while I am concerned that sys-whonix-14 is starting when I am NOT updating anything eg in dom0 today : qvm-run -a fooappVM fooapplication (for a fooappVM that wasn't open) and sys-whonix-14 was shutdown for some reason it started up my /etc/qubes-rpc/policy/qubes.UpdatesProxy ; looks like this : -- # Default rule for all TemplateVMs - direct the connection to sys-net $type:TemplateVM $default allow,target=sys-whonix-14 $tag:whonix-updatevm $default allow,target=sys-whonix-14 $tag:whonix-updatevm $anyvm deny ## Note that policy parsing stops at the first match, ## so adding anything below "$anyvm $anyvm action" line will have no effect ## Please use a single # to start your custom comments # Default rule for all TemplateVMs - direct the connection to sys-net $type:TemplateVM $default allow,target=sys-net $anyvm $anyvm deny -- It is in this order, because it works and a bit fearful to change it , but curious what others looks like and maybe it is obvious what the problem is ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/eb13f022-47e1-0f88-fe04-b62dc8bcc175%40riseup.net. For more options, visit https://groups.google.com/d/optout.
