-
-
Notifications
You must be signed in to change notification settings - Fork 52
Description
The problem you're addressing (if any)
sdwdate-gui has been rewritten to overcome shortcomings in its original implementation, and to allow Kicksecure qubes to show their sdwdate user interface in the global sdwdate-gui menu provided by sys-whonix. In order for this to work, it will be necessary for Kicksecure qubes to be able to call the sdwdate.Connect and sdwdate.ConnectCheck qrexec calls in sys-whonix. I will be submitting an update to qubes-core-admin-addon-whonix that provides the proper configuration for these calls to work for properly tagged VMs, and tags Whonix qubes properly.
Currently there's nothing in Qubes OS that can tag a Kicksecure qube as a valid sdwdate-gui client. This must be overcome in order to resolve #7447. While this bug is very closely related to the linked bug, I'm treating them as separate as the request here is a vital part of the fix, but not the entire fix.
The solution you'd like
Add a new package, qubes-core-admin-addon-kicksecure that will tag Kicksecure qubes with the needed sdwdate-client tag, very similar to how qubes-core-admin-addon-whonix already works.
The value to a user and who that user might be
People can use Kicksecure qubes without getting bombarded with qrexec denial error messages.
Completion criteria checklist
(This section is for developer use only. Please do not modify it.)