@drscriptt so there I am on the phone with tech support for a database vendor and he explains that licensing isn't working because #SELinux is enabled, so I set it to permissive, log the errors, make an appropriate permissions list, compile and turn it back on.
He says "nobody in house has made it work with SELinux on" -- obviously none of them spent 15 minutes learning how to use the tools. Ugh. #rant
@drscriptt @Madagascar_Sky @geerlingguy see also "just turn off #selinux" on every package.

as god is my witness, i have no idea what caused this, what a chr_file is, why there's a fprintd process, what chr_file 059 is, or what i should do about this

if windows threw this error i would scan for viruses and reboot

maybe i need to reboot

#SELinux #Fedora

コンテナ向けセキュリティプロファイル生成ツールの紹介 - Qiita

はじめに 記事を開いていただきありがとうございます。三菱電機の佐々木です。 本記事では、デーモンレスなコンテナエンジンであるPodmanを対象に、コンテナ向けセキュリティプロファイルの作成を支援するツールについて紹介します。具体的には、seccomp用のoci-secco...

Qiita

You know, I think I understand the gripes of people with SELinux as the damned thing can be a bunch of nonsense. Not because it's actually bad, but because complexity can cause unique problems on computers.

I think that I've had my fill of touching computers today and just want to play a game. Probably on my console, as I don't have to get too deep in the reeds with troubleshooting that thing.

#openSUSE #seLinux

Seems like I fixed my SElinux problems, after a big openSUSE Tumbleweed update. Seems like "touch /.autorelabel" and a reboot helped for the time being. As sometimes an update can introduce unexpected issues into one's system.

This is natural and expected so I didn't panic at all, just hunted for a solution for the first two hours of my day (unfortunately dodging breakfast).

There is also another fix that is coming down the pipeline for all users soonish...Thankfully, I won't have to dig any deeper for the time being.

As my understanding of SElinux is very scant (some solutions required truly knowing what you are doing) and I need to eat instead of hyper-fixating on learning something.

#Linux #seLinux

SELinux больше не враг, а помощник, или как мы подружили его с админами

Привет, Хабр! Меня зовут Ольга, я инженер по автоматизации в компании РЕД СОФТ. Моя работа – превращать сложные и рутинные задачи системных администраторов в простые и понятные конфигурации в РЕД АДМ. Сегодня поговорим о системе, которая у многих администраторов вызывает легкую (или не очень) дрожь – о SELinux.

https://habr.com/ru/companies/redsoft/articles/1002888/

#SELinux #Безопасность #Администрирование #администрирование_linuxсистем #DevOps #РЕД_АДМ #Linux #Автоматизация #Управление_конфигурациями #Open_Source

SELinux больше не враг, а помощник, или как мы подружили его с админами

Привет, Хабр! Меня зовут Ольга, я инженер по автоматизации в компании РЕД СОФТ. Моя работа – превращать сложные и рутинные задачи системных администраторов в простые и понятные конфигурации в РЕД АДМ....

Хабр

Well, I've been fighting #selinux and rootless #podman the whole day.

My plan was to run a #forgejo runner container in a minimal, secure and self-updating environment. And the thing is, I'm probably 95% there, but I can't get this stupid permission fixed for the podman socket. 🤷‍♂️

@Larvitz also #selinux has gotten so much better at adding other applications that there's really no good reason to turn it off nowadays.

Stop running setenforce 0 and pretending SELinux doesn't exist.

I wrote a practical guide to actually working with SELinux on Fedora and RHEL: Contexts, booleans, troubleshooting denials, container volume labels, and the commands you'll actually use.

No policy theory rabbit holes. Just the stuff that gets you unstuck.

https://blog.hofstede.it/selinux-a-practical-guide-for-fedora-and-rhel/

#SELinux #Fedora #RHEL #Linux #sysadmin #infosec #itsec

SELinux: A Practical Guide for Fedora and RHEL

Moving beyond “setenforce 0” - a practical guide to understanding, troubleshooting, and working with SELinux on Fedora and Red Hat Enterprise Linux.

Larvitz Blog