Skip to content
This repository has been archived by the owner on Jun 24, 2023. It is now read-only.

Avoid hard-coding dom0 in qubes-video-companion script #15

Open
DemiMarie opened this issue May 3, 2021 · 3 comments
Open

Avoid hard-coding dom0 in qubes-video-companion script #15

DemiMarie opened this issue May 3, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@DemiMarie
Copy link
Collaborator

DemiMarie commented May 3, 2021

On my system, webcams are attached to sys-usb. One alternative is to specify the target in qrexec policy instead. I will fix this.

@ElliotKillick ElliotKillick added the bug Something isn't working label May 8, 2021
@ElliotKillick
Copy link
Owner

Yeah, I wasn't quite sure how qrexec-client-vm would work for specifying multiple possible target qubes as it only allowed for specifying one. I figured if I just specify dom0 then because I've installed the qrexec policies (in the RPM package) in dom0 that should work for sys-usb (there is a policy added to allow sys-usb) too.

Is this assumption incorrect or is this alternative you're talking about just a better way of doing this?

@DemiMarie
Copy link
Collaborator Author

Yeah, I wasn't quite sure how qrexec-client-vm would work for specifying multiple possible target qubes as it only allowed for specifying one. I figured if I just specify dom0 then because I've installed the qrexec policies (in the RPM package) in dom0 that should work for sys-usb (there is a policy added to allow sys-usb) too.

Is this assumption incorrect or is this alternative you're talking about just a better way of doing this?

I usually use @default and use target= to direct the call to the correct qube.

@ElliotKillick ElliotKillick added enhancement New feature or request and removed bug Something isn't working labels Jun 20, 2021
@pietrushnic
Copy link

I have the same problem using v1.0.0-1 deb

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants