Lennart Poettering on Nostr: It's in fact so drastic that it even kills PID 1 if it is currently in the process in ...
It's in fact so drastic that it even kills PID 1 if it is currently in the process in writing its pretty status update messages to the console, instantly killing your system. (Because of this, PID 1 will only briefly open the console when doing an update, but it's still racy)
Moreover the kernel SAK concept is relatively easy to circumvent: if a user has access to the console, and their processes that have the console open is killed then nothing stops it to immediately reopen the console…
Published at
2024-11-07 11:16:34Event JSON
{
"id": "aee10be659a323e67b8bda1fd01a4b663e6515727c588932efa72cbef693fc70",
"pubkey": "1d95c32d9a9d95a54f98eb2eaa156f3d3a71dc49eca2c960b2b89962758f1cc0",
"created_at": 1730978194,
"kind": 1,
"tags": [
[
"e",
"0cd948d0b0d4cafe84d07c99a3f2c622763102f67b0a35b96bdfbe425e8312cd",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/pid_eins/statuses/113441386934639615",
"activitypub"
]
],
"content": "It's in fact so drastic that it even kills PID 1 if it is currently in the process in writing its pretty status update messages to the console, instantly killing your system. (Because of this, PID 1 will only briefly open the console when doing an update, but it's still racy)\n\nMoreover the kernel SAK concept is relatively easy to circumvent: if a user has access to the console, and their processes that have the console open is killed then nothing stops it to immediately reopen the console…",
"sig": "74033ecbba53c09e6563a23e53c9f5981dd1392e95583a4aeaf6b1f6fa5eecd9590b77438f2e312920388b03fd382d7468204524abf0d8337dc7801b219af05f"
}
