Video group grants access to two distinct hardware categories

[WhyNotHugo]

There are two distinct sets of hardware that are owned by group video:

• Video rendering devices (e.g.: drm).
• Video input devices (e.g.: webcams).

On a typical Wayland setup, a dedicated daemon arbitrates access to video rendering devices (e.g.: seatd) and allows only a single process (generally a compositor) to access the hardware. Other processes are denied access to the video rendering hardware.

This is considered a security measure, and prevents arbitrary user processes from screen-scraping, or screen-spoofing.

However, in order to use a webcam, a user must be a member of the video group, which breaks the above security measure entirely.

I believe that one potential fix for this to change the ownership of webcams to the camera group. This is, however, a breaking changing where all downstreams will need to adapt.

[WhyNotHugo]

Relevant rules are here: https://github.com/eudev-project/eudev/blob/7d1085839f8a5426c0a94ff35ca4fcb924ab1c07/rules/50-udev-default.rules#L32-L37

[bbonev]

I think that the best way for this is to get it adopted downstream. Starting from eudev will only bring breakage and confusion. And after getting it adopted in distributions, we can include it in eudev upstream. Did you work with a distribution that uses eudev regarding this change?

[WhyNotHugo]

I've proposed addressing this on the Alpine side as well. I think that before actually proceeding there needs to be some consensus that my suggestd approach is okay on all sides.