kurtseifried

Public Key

npub1063rn8w9d4cv0f7nhgefy37ayase2k3g5j4ja3vsw3vkc66asnlqazeaeu

NIP-05 Address

kurtseifried_at_infosec.exchange@momostr.pink

Profile Code

nprofile1qqs8ag3enhzk6ux85lfm5v5jglwjwcv4tg52f2ewckg8gktvddwcflsprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hspf79kq

Publishing to

relay.snort.social

relay.damus.io

nos.lol

Author Public Key

npub1063rn8w9d4cv0f7nhgefy37ayase2k3g5j4ja3vsw3vkc66asnlqazeaeu

Show more details

Last Notes

2024-09-05 17:34:09 UTC

- reply

this vastly over sells SELinux. In past I would have said please provide a list of CVEs actually mitigated by default SELinux policy, and conveniently enough Red Hat just posted an article https://access.redhat.com/solutions/7032454 TLDR there’s 6 CVEs mitigated by SELinux in 10 years. That’s less than 1% of the CVEs fixed in RHEL.
SELinux is needed by entities like the US DoD and NSA, https://www.nsa.gov/portals/75/documents/what-we-do/research/selinux/documentation/presentations/2005-flexible-support-for-security-policies-into-linux-os-presentation.pdf and was invented in an era to solve problems, but largely do not exist anymore, or rather if you run software in containers, like most of the world issues largely go away.
App armor is about as ineffective as SELinux and again from an error, where the correct answer to a lot of this is to use things like containers and more modern solutions.
Unfortunately, a lot of my old writing from 25 years ago is no longer available on the Internet, but the basic point I would make is that Lennox and armor are 25 year-old solutions to a world that has changed significantly.