Re: CUPS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2007-08-21 at 21:03 -0500, mark wrote:

> <Location /admin>
> #
> Order Deny,Allow
> Deny From All
> Allow From 127.0.0.1
> Allow From 192.168.0.0/255.255.255.0
> 
> #Encryption Required

I missed the first part of this thread, but if this is the CUPS web gui
served by Apache, try:

<Location /admin>

order deny,allow
deny from all
allow from 192.168.0.

</Location>

AFAIK, Apache doesn't use network/subnet mask style syntax.  You'll also
need to restart apache via something like "apachectl graceful" or
"service httpd restart".

BTW - The Apache documentation states you should use <Directory> rather
than <Location> to secure website access.  From the Apache 2.0.x
documentation:

"It is important to never use <Location> when trying to restrict access
to objects in the filesystem. This is because many different webspace
locations (URLs) could map to the same filesystem location, allowing
your restrictions to be circumvented."

See the following document, particularly the "What to use When" section
(recently learned this myself):
http://httpd.apache.org/docs/2.0/sections.html

-Eric

-- 
Eric Sisler <esisler@xxxxxxxxxxxxxxxxxxxxx>
Library Network Specialist
Westminster Public Library
Westminster, CO USA

Linux - Don't fear the Penguin.
Want to know what we use Linux for?
Visit http://wallace.westminster.lib.co.us/linux

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux