4 ms·
The screen-grabbing app would have to interface with the compositor instead of the display server. For example, krfb is adding Wayland screen sharing support wi
by sp332 7y ago
The screen-grabbing app would have to interface with the compositor instead of the display server. For example, krfb is adding Wayland screen sharing support with KDE.
- jandrese 7y agoIs this better from a security standpoint? Does the compositor verify clients in a more secure fashion? Presumably screenshotting is still a thing on Wayland so this has to be a solved problem.
- Bnshsysjab 7y agoThe point is apps can’t grab other apps input/output. If you run the app in an otherwise secure manner (eg execute in a perfect security chroot/container). A malicious application on your host can still do anything at the executing privilege level (read .ssh, inject malware into .bashrc) but can’t sniff your gksudo password
- michaelmrose 7y agoWhy would you assume it's a solved problem? Basically every compositor has to implement this feature.
- kelnos 7y agoThe idea is that the compositor can then pop up a dialog saying "App X wants to record your screen. Allow?"
- sp332 7y agoIt could also limit recording to certain windows, or heck even redraw the whole screen any way it wants, like pretending sensitive windows aren't there.
- Bnshsysjab 7y agoDoes this lead to a more fragmented application space? If each compostor required its own screen grabbing tool, and each DE has its own compostor?
- PlutoIsAPlanet 7y agoWhilst backend implementations are going to be different per-compositor, they're exposed as freedesktop apis so tools shouldn't need to be adjusted for each one.
- Bnshsysjab 7y agoI respect what your saying, but I’ve seen that model tried and failed multiple times