This should be a much friendlier SAK implementation:...

This should be a much friendlier SAK implementation: the original session is not terminated, but just switched away, taking away control of the keyboard, mouse and screen, without chance for the unprivileged code to interfere.

Note that before this actually becomes useful the display managers of the various desktop environments need to be updated to watch for the SAK signal. But the groundwork is laid now.

And that's it for today.

Like 7 November at 11:23 | Open on mastodon.social

4 comments

Anselm Schüler

@pid_eins Can I define a custom key combination? How are alternate keyboard layouts handled (e.g. Mac)?

7 November at 11:44 | Open on ieji.de

marius

@pid_eins is DBus robust enough for this kind of security mechanism? I would have thought that systemd can do something more drastic like freezing all sessions and switching to a "login" target :D (speaking as someone very far out the sidelines)

7 November at 12:31 | Open on metalhead.club

Lennart Poettering

@mariusor well, if dbus is hosed, systemd is pretty much hosed, too. SAK is probably the least of you problems then.

7 November at 13:57 | Open on mastodon.social

marius

@pid_eins I understand, I think I was asking more in the idea of this SAK message having to be secured some way against being intercepted by malicious listeners. I guess I don't really know enough about the situation to actually form a pertinent question, sorry. :)

7 November at 14:02 | Open on metalhead.club