Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 485
    • Issues 485
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 23
    • Merge Requests 23
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #2840

Closed
Open
Opened Sep 16, 2013 by Tomás Fernández@estopero

Add full support for SELinux / AppArmor

It would be fantastic get SELinux and AppArmor full support. Mixing some changes in the ISPConfig core/task behaviors and maybe creating/configuring the necessary SELinux/AppArmor rules to coexist happily with ISPConfig.

I know this matter has been discussed before, however I actually think is neccesary add selinux and apparmor support in ISPConfig. AppArmor works more or less with ISPConfig (Ubuntu), but SELinux kills it, and SELinux is configured and enabled by default in CentOS/RHEL for one reason, likely the most used distribution in the enterprise scope.

I love ISPConfig but it does not grant enough security level to replace SELinux and this is a very important tool to keep our servers safe specially in enterprise production servers, in my opinion it should be a priority for systems technicians like I'm sure ISPConfig creators are.

There are other ISP Managers (Not many of them, and I don't want publicize them here) with SELinux support and this point makes some comercial solutions a more affordable solution for enterprise production servers in the security side (ISPConfig is very very comfortable in other sides). I think adding SELinux/AppArmor full support in ISPConfig could be a huge improvement.

I would be happy if you would implement an "issue/ticket" focused donation system to give you a motivation to implement some features.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#2840