You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Yoom Nguyen <yo...@hostwebase.com> on 2008/10/15 13:53:14 UTC

[users@httpd] Apache directory access & Suse AppArmor


Can anyone tell me what is the different between Apache2 directory access as compare to AppArmor come with SuSE? 



I though SuSe AppArmor allow administrator to control the files, directory system level access.  And 

If you define something like these syntax below it will allow administrator to controlling the network layer access. 



<Directory "/images/"> 



Options None 



Order deny,allow 



                                Deny from all 



Allow from 65.123.86.50/255.255.255.248 



                </Directory> 





At the moment the above setting syntax will not do anything.  User still have access to above directory if I define and allow it within 

Yast2,  AppArmor. 











Can both function Apache2 access control and Suse AppArmor working together or only one can work at a time? 







Any help to clear my head will be appreciate. 







Y

Re: [users@httpd] Apache directory access & Suse AppArmor

Posted by Eric Covener <co...@gmail.com>.
On Wed, Oct 15, 2008 at 7:53 AM, Yoom Nguyen <yo...@hostwebase.com> wrote:
> Can anyone tell me what is the different between Apache2 directory access as
> compare to AppArmor come with SuSE?

They're independent, and you need to satisfy both to successfully
serve a file. Just like Apache config and traditional filesystem
permissions.


> <Directory "/images/">

This should be a physical on-disk directory, not a URL-path or a
directory name under your document root. If there's no literal
directory /images/ in your filesystem, this snippet configuration
never applies.

-- 
Eric Covener
covener@gmail.com

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org