RE: https://mastodon.social/@connel/115323672457296682

It turns out this issue was caused by #SELinux

I'm going to try and spend some time learning how it works to see if I can get it fixed.

There's a few other SE Linux violations that are logged on start up that I hadn't noticed.

Switching it off is also an option but I'll do some learning first. Not the first time I've found out this was the root cause of something not working that I've spent a lot of time debugging. Seems overkill for my little homelab.

Set scene.
At the Hackerspace.

Him: "I installed Fedora to test selinux."

Me: "Do you regret it yet?"

Him: "Well, it has failed so hard now that it refuses to boot."

Him: "I can't remember the last time I fucked up Linux so hard it refuses to boot."

#Linux #selinux #security

Judging by the amount I have run into #SELinux related issues while working with #RHEL based servers and my current #Fedora workstation setup I start to wonder if the enhanced security is worth all the trouble... 😮‍💨

Example: SELinux blocked my private key file for my OpenVPN config. OpenVPN resfused to start without giving a helpful error message. journalctl was helpful and I could then create a specific SELInux rule. It takes some experience to figure this out.

How is a "normal" computer / #Linux user supposed to figure this out without spending several hours? 😅