Context: A few days ago Arch pushed out a legitimately broken update. This was because they shipped out a testing version of util-linux. They very quickly fixed this… except I use SE Linux (say what you will I wanted to dive into it) and now I’m stuck waiting for the maintainer to update the AUR package so I can fix my system. This is not a general arch problem but a me problem because of my less standard, more niche build. Although the wait is genuinely making me reconsider using SE Linux as it’s been a hassle to maintain (just to keep things up to date, I gave up on keeping it in enforcing mode).

  • prettybunnys@sh.itjust.works
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    7 months ago

    If you’re not running SELinux in enforcing mode and you’re not developing policy then you’re really not doing anything with it, for what it’s worth.

    SELinux without a policy similar to a targeted policy seems not advisable on a rolling release system, unless you are actively maintaining a policy for the use case or your upstream package maintainers are releasing robust policy for everything

    • The Stoned Hacker@lemmy.worldOP
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      7 months ago

      It was a way to learn how to actually use SE Linux and its different components. I still have more that I wanna do with it, but it’s one of those projects that’s been on the back burner for a while