If you try to remove one of the predefined zones from Firewalld, e.g. public, you encounter the following error:

Error: BUILTIN_ZONE: 'public' is built-in zone

I don’t like that Firewalld is bloated with all of these built in zones that I will never use. I want to get rid of them, but, from what I’ve been able to find, it appears non-trivial to do so.

EDIT (2024-01-27T01:55Z):

I came across this GitHub issue. So it appears that this is a known “issue”, and it could potentially be changed in the future, albeit probably far in the future. It is a very strange initial design choice, though, in my opinion.

  • SheeEttin@programming.devEnglish
    2·
    10 months ago

    Because it aligns with most people’s use case. You’re free to patch it out if you’re so inclined.

    • Kalcifer@sh.itjust.worksOP
      1·
      10 months ago

      Because it aligns with most people’s use case.

      Sure, that is why we have defaults, but why force them? Why not create the defaults, and then allow the user to remove them if they wish?

      You’re free to patch it out if you’re so inclined.

      This is somewhat of a non-answer. Technically, yes, it is possible for a user to patch OSS as they see fit, but that does not excuse poor design desicions, nor is it necessarily fair to expect the user to do that.