Hello everyone.
Am I the only one getting the message “Whonix 17 deprecated”-alike while starting template, or it’s dvm’s dispvm?
I tried in-place upgrade, which went ok, but now getting error “Denied sdwdate. ConnectCheck from dispvmxxx to sys-whonix”.
Any feedback?
There is no Whonix 18 yet, so what/how did you upgrade?
What’s the exact message?
You’re probably using the developers repository - don’t.
Impact: Breaks sdwdate-gui: Secure Distributed Web Date Graphical User Interface.
To silence that error, run…
In Template:
sudo systemctl mask sdwdate-gui-qubes-proxy-helper.service
Indeed.
Once available it will be announced in the usual places. (Follow Whonix Developments)
related:
Primarily, pull request QubesOS/qubes-core-admin-addon-whonix#21 has been merged for Qubes R4.3 but we didn’t backport it to Qubes R4.2 yet.
This would cause qrexec
sdwdate.ConnectCheckdenied messages on Qubes R4.2.
Thanks for the feedback, @adrelanos. In addition, for some weird reason. when I try to update Whonix 17, qubes-contrib repo goes to trixie, instead to stay on bookworm…
What are the consequences of silencing that notification? Any security related?
.
Thanks. I did read the topic, but what I’m not comprehending is does it just blocks gui, or service itself… I’d like to know in general, not strictly related to this specific issue that caused the message about denying sdwdate. On the other hand, the message is pretty self-explanatory: sdwdate is denied to check the connection, as it is written…
It breaks sdwdate-gui. End of story.
sdwdate.ConnectCheck is implementd in sdwdate-gui package only.
Calling the qrexec service sdwdate.ConnectCheck instead of sdwdate-gui.ConnectCheck can be considered a minor bug.
You can Search the Source Code for file or string sdwdate.ConnectCheck.
