1 |
Hi folks, |
2 |
|
3 |
As per bug #368795 [1] we have an open request to include a SELinux policy |
4 |
module for the nginx webserver. However, while working on this, I remembered |
5 |
a small discussion that upstream had about the same matter [2]. It boils |
6 |
down to the question: do we support nginx within the existing domains (the |
7 |
apache SELinux module is generic enough to include support for other |
8 |
webservers as shown by its current support for lighttpd) or do we use a new |
9 |
module for this? |
10 |
|
11 |
[1] https://bugs.gentoo.org/show_bug.cgi?id=368795 |
12 |
[2] http://oss.tresys.com/pipermail/refpolicy/2011-March/004135.html |
13 |
|
14 |
The thread upstream didn't give a clear signal in my opinion here. On the |
15 |
one hand was there a mail that said "we should have a specific nginx |
16 |
module", but the reasoning behind it was countered. Yet the patch itself (to |
17 |
include nginx support in apache module) isn't pushed to the repository. |
18 |
|
19 |
Our current "policy" [3] here (what's in a name) has no clear answer on it. |
20 |
We do say we want to track upstream as closely as possible (and make sure |
21 |
that our customizations do not interfere with it) but that doesn't give a |
22 |
signal in either direction. |
23 |
|
24 |
[3] http://goo.gl/2U0Zr |
25 |
|
26 |
My /personal/ vision here is that we eventually would need a |
27 |
capability-based module ("webserver") with specific implementations that use |
28 |
the interfaces/templates from the generic one for their specific |
29 |
implementations ("nginx", "apache", ...) but _that_ does not work with the |
30 |
current upstream implementation (or way of working). |
31 |
|
32 |
So... ideas? Do we want to "keep it simple" and update the apache policy to |
33 |
support nginx? Or do we want to stay "least privilege" and have dedicated |
34 |
rules for applications? |
35 |
|
36 |
Or do we see if we can deviate from upstream here and start our own path (in |
37 |
my opinion, we can't as long as we do not have a critical developer mass - |
38 |
in numbers, not in kilogram). |
39 |
|
40 |
Wkr, |
41 |
Sven Vermeulen |