Ticket #538 (closed enhancement: fixed)

Opened 2 years ago

Last modified 8 months ago

Ship Midgard with SELinux policy files

Reported by: bergie Assigned to: jval
Priority: major Milestone: 8.09.4 Ragnaroek
Component: Midgard Data Version: 8.09 Ragnaroek
Keywords: Cc:

Description

Several Linux distributions come with SELinux. It would be a good thing to ship Midgard with appropriate SELinux policy files.

http://www.linuxjournal.com/article/8766

Change History

12/15/08 14:40:24 changed by bergie

  • milestone changed from 8.09.3 Ragnaroek to 8.09.4 Ragnaroek.

02/10/09 15:44:55 changed by jval

  • status changed from new to assigned.
  • component changed from Midgard Data to Midgard Apache.

It would require working on the actual platforms to make the policy modules for all the distributions and for all of their policies.

For Fedora based distributions (Fedora, Red Hat Enterprise Linux, CentOS etc.) this can be done by me.

There are three policies currently in Fedora: strict, targeted and mls. I'm thinking perhaps we could first settle for having a working targeted policy module because that's the one we really desperately need (because Fedora based distributions ship with SELinux targeted policy enabled by default)...

02/10/09 15:46:55 changed by jval

(In [20395]) SELinux targeted policy files for Fedora based distributions, refs #538

03/09/09 12:35:59 changed by jval

(In [20940]) Add Fedora related files to make dist, refs #538

03/09/09 12:53:57 changed by jval

  • priority changed from minor to major.

In my opinion this ticket should be taken as "make policy modules for all distribution policies which are enabled by default". And as far as I know it, Fedora's targeted policy is the only one which is enabled by default.

Supporting the default distribution settings is kind of important (as without having this Midgard doesn't work without knowledge of how to tweak the SELinux configuration), so I'm raising the priority of this ticket.

03/09/09 13:12:04 changed by jval

<bergie> jval: feel free to edit the ticket and close it :-)

Ok. So I'm taking this ticket as I told above. Which means basically this ticket is now fixed.

03/09/09 14:13:21 changed by jval

(In [20951]) Add spec files based on Fedora Packaging Guidelines. Fixes #941, refs #538

(follow-up: ↓ 19 ) 03/09/09 14:58:22 changed by jval

  • status changed from assigned to closed.
  • resolution set to fixed.

Now we have Fedora/EL SELinux targeted policy source files as well as Fedora/EL RPM spec files which handle the SELinux targeted policy out-of-the-box (you can create binary rpms from those if you have a Fedora based OS like Fedora >= ?, RHEL >= 5 or CentOS >= 5).

It would be nice if the OBS binaries would also handle the Fedora/EL SELinux targeted policy out-of-the-box. But that's another issue and I've created a general ticket #943 about that.

Closing this ticket now as fixed.

03/11/09 17:30:56 changed by jval

  • status changed from closed to reopened.
  • resolution deleted.
  • component changed from Midgard Apache to Midgard Data.

Oh I've made a mistake by adding the SELinux files to mod_midgard. The whole policy (e.g. file contexts) reflects the way how datagard configures the system so clearly the policy should be shipped with midgard-data instead of mod_midgard.

I need to change that to keep things consistent...

03/11/09 17:43:38 changed by jval

(In [21043]) Move the SELinux policy files from mod_midgard to midgard-data, refs #538

03/11/09 17:55:50 changed by jval

(In [21044]) Remove the selinux subpackage. Refs #538, refs #941

03/11/09 18:31:52 changed by jval

(In [21051]) Rename the SELinux policy module from modmidgard to midgard, refs #538

03/11/09 18:34:39 changed by jval

  • status changed from reopened to closed.
  • resolution set to fixed.

(In [21054]) Add the selinux subpackage. Fixes #538, refs #941

03/12/09 11:57:16 changed by jval

(In [21059]) Add versioned selinux-policy dependency to ensure binary compatibility. Refs #941, refs #538

03/12/09 12:11:17 changed by jval

(In [21060]) Fix the changelog dates to reflect the latest change dates. Refs #941, refs #538

03/12/09 13:15:11 changed by jval

(In [21063]) Simplify package names and dependencies. Refs #941, refs #538

09/01/09 13:22:58 changed by jval

(In [23264]) Allow midgard-data-selinux to be older than midgard-data and move its dependency to midgard-cms-server. Refs #941, refs #538

09/01/09 13:53:37 changed by jval

(In [23265]) Forgot to keep midgard-data dependency in midgard-cms, fixing now. Refs #941, refs #538

(in reply to: ↑ 8 ) 10/12/09 17:05:44 changed by jval

Replying to jval:

Now we have Fedora/EL SELinux targeted policy which handle the SELinux targeted policy out-of-the-box It would be nice if the OBS binaries would also handle the Fedora/EL SELinux targeted policy out-of-the-box. But that's another issue and I've created a general ticket #943 about that.

#943 is now implemented which means Midgard supports SELinux now fully. Which in turns means you don't have to worry about SELinux when installing Midgard on Fedora/EL. Just use the rpms and it just works. :)

01/21/10 15:20:07 changed by jval

(In [24835]) Add memcached support to the midgard selinux policy module. Updated midgard.pp from 1.0.0 to 1.1.0 in the midgard-data-selinux OBS package. Refs #538, refs #941, #refs #943