D17097: [scripting] Emit clientAdded for Wayland clients
Martin Flöser <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kwin |
|---|---|
| Message-ID | <[email protected]> |
graesslin added a comment. In D17097#364320 <https://phabricator.kde.org/D17097#364320>, @zzag wrote: > In D17097#364318 <https://phabricator.kde.org/D17097#364318>, @graesslin wrote: > > > (e.g. dedicated permissions for accessing dbus). > > > So, it would be something similar to what web browsers have when it comes to extensions(e.g. "Access your data for all websites", "Read and modify privacy settings", etc)? That would be a possible idea on how one could implement it. I could think of metadata defines what extensions it uses (e.g. dbus, global shortcut, read settings, screenedge, etc...) and on first load the user needs to ack these settings. For a not acked setting the calls would just not work. The problem with the approach is that we cannot secure the kwinrc to which it is written. So the whole thing doesn't really work as long as all processes can write kwinrc. On the other hand it could protect properly sandboxed flatpacks. Btw. I don't think we need to discard the reviews. I could also see a solution in disabling the dbus extension on Wayland or to say we ignore the security problems due to the point written above. REPOSITORY R108 KWin REVISION DETAIL https://phabricator.kde.org/D17097 To: zzag, #kwin Cc: mart, graesslin, kwin, mkulinski, ragreen, jackyalcine, Pitel, iodelay, bwowk, ZrenBot, lesliezhai, ali-mohamed, hardening, jensreuterberg, abetts, sebas, apol