<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 03/28/2012 12:56 PM, Daniel J Walsh wrote:
<blockquote cite="mid:4F730A72.1060609@redhat.com" type="cite">
<pre wrap="">Joe, I am not sure how this effects SELinux labeling, if it does at all.</pre>
</blockquote>
<br>
Afaikt this does not affect selinux in anyway since these are
configuration syntax changes for the most part.<br>
<br>
If we take this example which is common as an default in various web
applications...<br>
<br>
What used to be...<br>
<br>
<Directory "/var/www/example"><br>
Options Indexes FollowSymLinks<br>
Order allow,deny<br>
Allow from all<br>
</Directory><br>
<br>
Will become...<code> </code><br>
<br>
<Directory "/var/www/example"><br>
Options Indexes FollowSymLinks<br>
Require all granted <br>
</Directory><br>
<br>
etc...<br>
<br>
So what we as an project will need to do, is to update our
documentation and maintainers will have to update default apache
configuration to reflect the new configuration syntax for the
application/package they maintain.<br>
<br>
Administrators will have to updated their apache configuration(s)
accordingly and or install the mod_access_compat module. <br>
<br>
The new api changes can be found here [1].<br>
<br>
JBG<br>
<br>
<a class="moz-txt-link-freetext" href="http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html">http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html</a><br>
</body>
</html>