![]() Installation of course in template, run it in appVM. I don’t have, so I used my old android device with “IP webcam” app on template I installed v4l2loopback-dkms ffmpeg webcamoid adb, created dummy device with this script. Some laptops are built with couple internal PCBs, not everything is included on motherboard) But this is the worst case. (however on some notebooks/laptops might occur problem with external microphone when PCI device crashes. For Microphone I just attach it using Qubes GUI and it works well.(but let’s be honest it doesn’t guarantee privacy at all, as said above, better use dispVM). I don’t trust proprietary conferencing too, so I created separated Debian template for it.Could that still happen after I’ve detached them from the qube? Could a compromised mic/webcam attack sys-usb or other qubes later on? Are there any best practices here? (I could always cover the webcam, so the mic is my bigger concern here.) Suppose I trust a laptop’s built-in webcam and mic, but I don’t trust proprietary video conferencing apps not to compromise those devices, keep them activated after I quit the app, etc. How would screen-sharing work? Zoom and others let you share a single application’s window could I screen-share other applications if they’re in the same AppVM/DispVM? What if they’re running in a separate AppVM? What about screen-sharing the whole desktop? (I know it’s a risk to show the world what your desktop looks like, but I’m just wondering.) ![]() I’m new to Qubes and excited to try it out soon, but I’m curious about how videoconferences (Jitsi, Zoom, Teams, Meet, etc.) work in Qubes.īased on some of the other posts I’ve read on here, it seems as simple as attaching a webcam and mic (which I assume normally live in sys-usb) to an AppVM or DispVM set up with the software I want to use. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |