A couple of notes on the previous emails,
Fabrice, so long as your app ensures that no third-party code can
programmatically grab a shortcut without user agreement, it would make sense to
let it have a privilege.
Quite obviously a compo should have the last word and be able to refuse a
request
Hi Michael,
> Is there any reason global shortcuts should lie with an application?
>Wouldn't it make more sense to provide an interface on the compositor
> side, where clients can register a global shortcut and the compositor
> sends an event back in case of the shortcut being pressed.
>
> In that
Hi Fabrice,
> Hi all,
> This topic came up in my previous one about window placement, and I'd like to
> go further.
> So currently there is no such thing as Global shortkeys and keyboard focus,
> however let me present a typical real use-case:
> [...]
>
> Now, I've read some vague things about pri
?Hello,
In a previous discussion on this ML [0] and blog article [1], Martin Peres
explained why Wayland should distinguish between normal and privileged clients
and what the security requirements for Wayland are. After that, I spent some
time thinking about how to handle the processes of autho
> Hi Steve, thanks for the thoughtful response.
>
> PAM's technical implementation allows a number of modules to be tried in
> order for authentication. Your API, as a PAM authentication module, is
> limited to four operations: ask the user a non-secret question (with a
> textual response), ask th
Hello Jasper,
A quick reply on some of your emails (grouped to avoid spamming the ML).
> My experience with PAM and similar "pluggable security modules" is that
> they provide a subpar user experience, are hard to integrate properly into
> the system, and have large pain points that stem from ha
