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.

There seems to be an issue with auth, as I can't login with this fedia.io account.

Looking forward to the upcoming pages.

Boop

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.

Works for me again too. Thanks for fixing it.

Likely a bug with the Anubis setup, as I noticed this issue after Anubis was enabled for fedia. So I think only @jerry@fedia.io or an upcoming Mbin version can fix this.

As the bowling ball is heavy it might also start spinning counterdirectional to the belt to stay where it is. When the belt stops later, the ball will roll to the left.

It’s quite aggrivating that the first half of the list space is wasted on irrelevant junk (random, pets, etc).

There was a recent update of Mbin, so I checked this and it seems to be fixed. Your crosspost should be possible now.

Very very pretty (✿◠‿◠)

Thank you for sharing this important information.