• heartsofwar@lemmy.world
    link
    fedilink
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    Fix the docs, improve error messages, and create a GUI to improve usage.

    All of that is fine to do, but it won’t fix the issue of many commercial software requiring SELinux to be disabled; that will only be fixed by the software companies actually embracing and supporting SELinux by creating rule sets to allow their software to work with SELinux.

      • heartsofwar@lemmy.world
        link
        fedilink
        arrow-up
        10
        ·
        1 year ago

        lack of documentation isn’t the problem

        The problem is that companies don’t want to spend the time learning SELinux and supporting their software with SELinux. I’m an embedded Linux engineer and I see this all the time: companies are barely able to reach their product deadlines as-is; heaven forbid you add another requirement like SELinux to the mix.

        • Kazumara@feddit.de
          link
          fedilink
          arrow-up
          10
          ·
          1 year ago

          Recently a supplier of ours announced that we could finally host their shitty java app on Linux instead of paying fucking Oracle for Solaris. So we were eager to hear the requirements. It was RHEL 8.4 or something, a version that was already EOL at the time.

          They can’t even update their distros apparently.