The difference in security defaults between Debian and Red Hat.

There has been a steady uptick of people stating that they will migrate (or already have) to Debian – seeking refuge from what they see as greedy corporate influence. I understand the sentiment fully. However, there’s a problem here that I want to talk about: security.

The ugly truth is that security is hard. It’s tedious. Unpleasant. And requires a lot of work to get right.

Debian does not do enough here to protect users.

Long ago, Red Hat embraced the usage of SELinux. And they took it beyond just enabling the feature in their kernel. They put in the arduous work of crafting default SELinux policies for their distribution.

…

However, its default security framework leaves much to be desired. Debian’s decision to enable AppArmor by default starting with version 10 signifies a positive step towards improved security, yet it falls short due to the half-baked implementation across the system.

…

The fundamental difference between AppArmor and SELinux lies in their approach to Mandatory Access Control (MAC). AppArmor operates on a path-based model, while SELinux employs a significantly more complex type enforcement system. This distinction becomes particularly evident in container environments.

…

The practical implications of these differences are significant. In a SELinux environment, a compromised container faces substantial hurdles in accessing or affecting the host system or other containers, thanks to the dual barriers of type enforcement and MCS labels.

TLDR: According to the author, Debian’s use of AppArmour is not as effective as RedHat’s use of SELinux when it comes to security.

  • FindmysecEnglish
    81·
    11 days ago

    You do know that you can run SELinux on Debian right?

    And MAC isn’t the end-all for security arguments

    • Leaflet@lemmy.worldEnglish
      7·
      11 days ago

      Are the default policies good though? There’s some collaboration between Fedora and Tumbleweed for SELinux policies, I imagine even more now since Tumbleweed plans to move to SELinux in the near future and derivatives like Aeon are already using SELinux.

      • Possibly linux@lemmy.zipEnglish
        11·
        11 days ago

        It depends on how you set it up and what software you are running.

        Use the defaults as a starting point and then move on from there

    • Possibly linux@lemmy.zipEnglish
      11·
      11 days ago

      You can lock it down really hard if you want to. Debian’s relatively simple design makes it so there are a lot less moving parts in my experience.