Adrian Vovk

~~Another thing to do: update the README~~ Done

What should I do about the test failure? Looks like your cmake build isn't being linked against a crypto library so the test can't run

Fixed that one

Bumping. The CI is failing because the cmake CI builds don't come with a crypto library. I don't know what to do about that The rest of the CI failure...

Yeah seems like something we can reasonably fix. I'll assign it to myself for now to eventually address it but if someone else wants to contribute the fix I'd appreciate...

Homed home dirs are supposed to be portable between machines. Different machines don't share /var. Hence ~/. identity is the canonical location of the user's settings, and /var as actually...

An easy way to pick a SAK that definitely won't conflict with anything is to involve the power button: Ctrl+Alt+Power, or Shift+Power, or similar

What's the point of a SAK? It's to prevent applications from pretending to be the OS by establishing a privilege boundary: the OS can respond to the keybind, but non-OS...

Perhaps a better (actually secure) way to implement this would be via some changes in the kernel The kernel already has a configurable SAK keyboard shortcut, that works despite raw...

Ah one last thing: even _if_ we get all the super fancy kernel stuff, logind will need to tell the running display-server about the SAK anyways. I think for GNOME...