In some usecases SELinux is less flexible:

You have two applications installed which bring their own labels and rules, lets say app_a_t and app_b_t. Now you want to give AppA read access to only one specific directory of AppB data (which is labeled app_b_t).

How to do that? Writing a rule allowing acces between the labels would give AppA access to all of AppB data. Creating a new label for this specific dir would break AppB as it relies on the rules for app_b_t.

My biggest issue with SELinux is that files and applications can not have multiple types at once (like with a role based model).

A hill to die on: AppAmor is better for most user setups.

I don’t think so about the post-facto decrypt. Keyexchange runs with the certs of the destination server. The cerst affected by the leak are intermediate certs which give trust to a cert chain AFAIK.

But some things are directories (like cgroups). And Networknamespaces were also controled in a weird way.
And then there are kernel features which are not exposed through a file or syscall but through a special type of socket.

xkcd

It can happen to others too. When I used Raspbian, two times (iirc) the upgrade process to the new major version broke while installing libc and so the system was bricked afterwards.

I think I read somewhere that the recomended upgrade process is to reinstall the system. How bad must updates be implemented in this case?

Are you aware that RAM is cleared on reboot?

Are you perhaps on Wifi? I noticed that Fedora is has configured Systemd to wait for online network before continuing starting the login services.

While Pomni is the hesitant type from time to time, she is also energic and not afraid of using her brain. So I think something like Fedora is more fitting for her. Gets the job done while allowing tinkering.

Mint on the other hand I would assign to Gangle. Calm and hard to break.