[Qubes OS 4.1] "Denied: whonix.NewStatus" dom0 permission

dom0:/etc/]sudo grep -r sys-old-qube

didn’t return anything

Isn’t line number and config file name in dom0 journal log?

1 Like

Not sure I understand your question, but journalctl is just full of:

 dom0 qrexec-policy-daemon[2530]: qrexec: whonix.SdwdateStatus+: sys-whonix -> various-qubes-names: allowed to various-qubes-names

and then every so often

qrexec: whonix.NewStatus+status: existing-qube -> non-existent-qube: denied: denied by policy
qrexec: target 'non-existent-qube' does not exist, using @default instead

But again, in /etc/qubes/policy.d/80-whonix.policy, all I have for NewStatus is:

 whonix.NewStatus * @tag:anon-vm  @tag:anon-gateway  allow  autostart=no
 whonix.NewStatus * @anyvm           @anyvm                    deny

no reference to ‘non-existent-qube’

Old non-existing VM name is in existing VM /usr/local/etc/sdwdate.d or /etc/sdwdate.d because you added it there previously and now forgot about it?

2 Likes

It was in /usr/local/etc/sdwdate-guid.d/50_user.conf, on the qube that was trying to connect to the non-existent qube. I even mention creating that file above :confused: Thank you!