So I installed qubes on a laptop so a sys-usb was created during installation so my usb keybaord didnt work (by design i guess) but I have edited the ```
/etc/qubes-rpc/policy/qubes.InputKeyboard added the line sys-usb dom0 allow and the keyboard still gets denied when I plug it in? The usb mouse works fine but keyboard no.
in my /etc/qubes-rpc/policy/qubes.InputKeyboard I have
I assume something needs to be changed but I am not sure what and dont want to bork my system by tinkering too much. I re-checked on my previous setup and apparently my /qubes.InputKeyboard is “stock” but the keyboard worked just fine there - I cant remember if I had done anything to get the keyboard working on the previous setup but it seems not?
That looks completely wrong to me.
What is that final line doing there?It is proper to the qrexec file ,
not the policy. Are you really editing the policy file? Check again.
I would change the policy file to:
sys-usb dom0 allow
$anyvm $anyvm deny
You could also use ask to confirm that the policy is being triggered
when sys-usb starts.
Leave the files in /etc/qubes-rpc/ alone.
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.
Strictly speaking, one should move to the new policy framework where
rules are laid down in policies under /etc/qubes/policy.d
The recommendation is that you leave Qubes provided policies alone and
override them with user policies of lower number - e.g. 10-user.policy
This makes it easier to identify user changes to the policies.
The policy syntax has changed somewhat, but it should be clear enough,
and you can always follow the examples in the Qubes provided policy
files.
For the moment you can continue to use the old policy files and old
syntax, but this is a transitional feature tat will be removed.
I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.