Hacker News Reader

Comment by TheLoafOfBread | Hacker News Reader

[flagged]

>people will disable SELinux the moment their distro boots first time, because that thing is just massive pain to use Linux with.

I think you mean secure boot: the only distros that even try to enable SELinux are Fedora and Red Hat, and on those distros SELinux gets in the way only very rarely. (Source: I am a user of Fedora and Red Hat.)

They definitely mean selinux. There only needs to be a single issue for an average user to disable selinux.

That's it! I was just having trouble connecting to my local rmq server on a fresh fedora 39 install. Forgot to disable selinux!

I always thought that admins of Linux installs other than Fedora and Red Hat installs rarely bothered with selinux and that it is definitely not enabled on an initial install.

I thought selinux was available as a package on non-RH distros, but install it and enabling was very painful unless you are an selinux expert, so almost no one on those distros does.

Are you sure you don't mean AppArmor?

I've been a fedora user and Red hat user since 2010, and worked at Red hat for a few years, though not on RHEL.

I think they did mean selinux. You are absolutely right that nowadays it just works for the most part. The big exception is for people deploying applications that don't have selinux config shipped by Red hat. Those people have to configure things properly, and rarely do people bother. If you do things like change the default ports for services, that can also get you in selinux trouble.

No, I mean selinux. And when I was using Linux, selinux got in the way basically immediately.

Interesting. On which distro?

Fedora if I remember correctly. It is few years back.

selinux should come with a GUI prompting for every operation. As I am aware, it cannot work in this mode.

Reply on news.ycombinator.com