New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow access to camera and microphone on WINDOWS 11 #1669
Comments
Curious, still on ToDo list? |
I mean it would be really helpful.
…On Mon, Jan 9, 2023, 3:15 PM bjm234 ***@***.***> wrote:
Curious, still on ToDo list?
—
Reply to this email directly, view it on GitHub
<#1669 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOO3VOQGF5QQHASXJM6WFZTWRRWW3ANCNFSM5QBQT4WQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Windows 11 has changed how the frame server for webcams is to be accessed, to get this working a larger re work of Sandboxies inner mechanics around COM/RPC Virtualization is required. As a preliminary workaround a Compartment Type Box can be used with opened COM access can be used
to mitigate for the reduced isolation it is recommended to prevent process elevation
|
Allow access to location/spoof location as well. |
It looks like both these settings are necessary for Zoom to detect a camera, and NoSecurityIsolation needs a license in order to work (for longer than 5 min at a time), unfortunately. NoSecurityIsolation, as I understand, encompasses a variety of sandbox changes. Do we know which one(s) specifically are relevant to camera access, and would it be possible to add just that particular permission as its own separate ini flag? |
Is your feature request related to a problem or use case?
I want to be able to use camera and microphone in the sandbox sometimes.
Describe the solution you'd like
Maybe add two check boxes that allow camera or microphone access.
Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: