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

Avoid checking out v4l2loopback before having verified the release tag #8

Open
DemiMarie opened this issue Apr 28, 2021 · 2 comments
Open
Labels
enhancement New feature or request

Comments

@DemiMarie
Copy link
Collaborator

Most of the vulnerabilities in git require having checked out the repository, which git clone does implicitly. Fortunately, Qubes Builder uses a script that doesn’t have this issue. I can make a PR for a standalone version.

@ElliotKillick ElliotKillick added the enhancement New feature or request label May 1, 2021
@ElliotKillick
Copy link
Owner

Yes, this would be highly appreciated Demi!

@ElliotKillick
Copy link
Owner

ElliotKillick commented Jun 20, 2021

Wouldn't it be best to just integrate the v4l2loopback driver in the Qubes Linux kernel? Of course, this would taint the kernel but I'm pretty sure it's already tainted through the side-loading of another non-mainline kernel module anyway.

What you're suggesting though could still be useful for direct integration into the Qubes Builder when it has to fetch the v4l2loopback driver for building the VM kernel.

Also, note that the v4l2loopack kernel module would of course not be enabled at boot to reduce attack surface.

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

2 participants