Windows 11, and the group policies doesn’t allow us to use WSL. We also can’t directly SSH into any servers so we have to go trough a Citrix session to a Windows 10 “admin server” and then SSH or RDP to a Linux server. And Windows Terminal isn’t installed on the Windows 10 server, so it’s either CMD or the Powershell terminal.
It’s absolutely fucking miserable. I’m a Linux sysadmin who do a lot of automation (ansible etc) but also Python development. Try it yourselves and see how long you last! I’m jumping the fucking ship in a month though, thank the gods.
All the result of an over confident “security organization”, with a lot of hubris.
But the best part? It’s a $5000 work laptop, and my 6 year old Thinkpad (with Linux) runs laps around the thing any day of the week. Opening the file explorer takes, most of the time, 5+ seconds…
Fuck my life, and fuck this company.
I definitely do not hate SELinux, I think it’s a great system. But my experience mostly (at home, anyway) comes from managing servers running Kubernetes clusters and, like, just using podman do deploy containers. In both these cases SELinux is a on “just works” basis, for the most part.
Then in enterprise environment that doesn’t run everything on containers, you usually have a very standardized way of applying SELinux policies. At my last place of work we did it via a rather Ansible role. It was simple and easy.
But I can imagine using SELinux at home, where you maybe don’t have these things, might be a rather “mysterious” experience. It’s not the most obvious system.
But learning to write your own policies (even if just trough se2allow or whatever it’s called) does de-mystify SELinix pretty quick.