SELinux bypasses

(klecko.github.io)

57 points | by voxadam 4 hours ago ago

4 comments

  • wannacboatmovie 23 minutes ago

    The problem with SELinux is it's very fragile and basically broken outside RedHat distros.

    As an experiment I installed SELinux on Debian and while I was eventually able to get it stable and working after a lot of trial and error, a disk swap followed by an rsync broke it irreparably. Yes I rescanned the disk or whatever to have SEL relearn/reindex the objects, didn't work. The box was basically unbootable or it would boot and rejected all logins, including root directly to the console, something that should nearly never happen. Documentation is sparse or assumes you have RedHat and it 'just works'. After hours of troubleshooting the only thing that worked was switching it off and saying good riddance.

  • rwmj 28 minutes ago

    I'm a bit confused by this article. If you have a way to write arbitrarily into kernel structures can't you pretty much do anything already?

    • DougMerritt 5 minutes ago

      On raw hardware, yes, but they're talking about running on a Samsung hypervisor.