-
-
Notifications
You must be signed in to change notification settings - Fork 52
Description
The problem you're addressing (if any)
Event buffering is now a feature of the GUI daemon, which can be set by modifying the gui-events-max-delay feature for any qube that uses the GUI daemon. Currently this feature can only be used by advanced users who know where to find the documentation for the feature (a blurb in /etc/qubes/guid.conf, which isn't even used by the GUI daemon anymore) and who are willing to fiddle with the qvm-features command in a Dom0 terminal. Whonix-Workstation VMs will hopefully come with the feature set to a reasonable default value of 100 ms once QubesOS/qubes-core-admin-addon-whonix#20 is merged, but just like kloak (the application that inspired the event buffering feature) is useful outside of Whonix, event buffering may be useful as well. Users need to be able to know the feature exists and how to configure it in order to use it.
The solution you'd like
We should provide some easy way to configure this setting, perhaps in Qube Manager.
The value to a user and who that user might be
Users can obfuscate keyboard rhythm biometrics from any VMs they want, regardless of OS, so long as they can interface with the GUI daemon.
Completion criteria checklist
(This section is for developer use only. Please do not modify it.)