On Thu, Oct 16, 2008 at 7:09 PM, Yoom Nguyen <[EMAIL PROTECTED]> wrote:
> ** This syntax and options will not allow any network to access *
>
> Options None
> Order deny,allow
> Deny from all
> Allow from 172.10.10.0/255.255.255.0
>
Show your error log and access log.
Allow from all
Thank you,
Y
- Original Message -
From: "Eric Covener" <[EMAIL PROTECTED]>
To: users@httpd.apache.org
Sent: Thursday, October 16, 2008 1:48:23 PM (GMT-0500) America/New_York
Subject: Re: [EMAIL PROTECTED] Apache directory access & Suse AppArmor
On
On Wed, Oct 15, 2008 at 10:55 PM, Yoom Nguyen <[EMAIL PROTECTED]> wrote:
> Eric,
>
> I got most of what you described but there are still something unclear to me.
> If I want the WHOLE directory /images to allow view by the OS (AppArmor) and
> deny view via the network by
> every other network exc
America/New_York
Subject: Re: [EMAIL PROTECTED] Apache directory access & Suse AppArmor
On Wed, Oct 15, 2008 at 8:52 AM, Yoom Nguyen <[EMAIL PROTECTED]> wrote:
> Eric,
>
> It seems if I enable /srv/www/domainroot/images/* via AppArmor then
> I don't even need to declare in
On Wed, Oct 15, 2008 at 8:52 AM, Yoom Nguyen <[EMAIL PROTECTED]> wrote:
> Eric,
>
> It seems if I enable /srv/www/domainroot/images/* via AppArmor then
> I don't even need to declare in Apache configuration
> file. Is this true?
It's true that making the files unreadable via the OS prevents Apa
Eric said:
>
>
> 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.
On Wed, 2008-10-15 at 07:52 -0500, Yoom Nguyen wrote:
> Eric,
>
From: "Eric Covener" <[EMAIL PROTECTED]>
To: users@httpd.apache.org
Sent: Wednesday, October 15, 2008 10:53:38 PM (GMT-0500) America/New_York
Subject: Re: [EMAIL PROTECTED] Apache directory access & Suse AppArmor
On Wed, Oct 15, 2008 at 7:53 AM, Yoom Nguyen <[EMAIL PROTECTED]&
On Wed, Oct 15, 2008 at 7:53 AM, Yoom Nguyen <[EMAIL PROTECTED]> 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 t
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
