Patrick Schleizer

Why did you close this issue?

Actually probably belongs to `/etc/qubes/policy.d/90-default.policy`. A Qubes developer (didn't check git history who) already defined Whonix related Qubes UpdatsProxy settings in `/etc/qubes/policy.d/90-default.policy`. Can be seen here: https://github.com/QubesOS/qubes-core-admin/blob/master/qubes-rpc-policy/90-default.policy#L63-L68 So perhaps just...

In https://github.com/QubesOS/qubes-core-admin/pull/487 legacy style `/etc/qubes-rpc/policy/qubes.UpdatesProxy` gets commented out, effectively doing nothing. This is using the same deprecation mechanism as used and approved (merged) in the past: https://github.com/QubesOS/qubes-core-admin-addon-whonix/blob/master/qubes-rpc-policy/whonix.GatewayCommand.policy Getting commented out...

Is there something else to do here such as Qubes salt? @marmarek

> Re-posting the comment I left in [QubesOS/qubes-core-admin#487](https://github.com/QubesOS/qubes-core-admin/pull/487) > > I was curious about this because I still use `/etc/qubes-rpc/policy/qubes.UpdatesProxy` to manage my updates through Whonix. If you modified it,...

Without cacher: There's also a fail-safe preventing Qubes-Whonix Templates updated over clearnet. The Templates check if they are connected to a torified Qubes UpdatesProxy. However, even update attempts through sys-net...

Now I understand. Thank you. In other words, a migration path for users who chose `updates-via-whonix.sls` (update all Templates using sys-whonix) to the new format needs to be added to...

`30-user.policy` seems like something only the user should edit. No scripts or operating system updates should interfere with it, edit it. If edited by scripts (such as salt) that seems...

@marmarek > Thanks @adrelanos for [QubesOS/qubes-core-admin#487](https://github.com/QubesOS/qubes-core-admin/pull/487). One remaining change is where the "update every template via sys-whonix" is set: https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/blob/master/qvm/updates-via-whonix.sls. I'll open PR for that one. Waiting for @marmarek.

I am not sure yet. Does this require a quick answer? > Another idea is to pass some different information - for example some approximate DPI value - like one...