You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by "R. P. C. Rodgers" <ro...@nlm.nih.gov> on 1997/03/27 17:30:01 UTC

config/270: access.conf does not support access from a single host specified by hostname

>Number:         270
>Category:       config
>Synopsis:       access.conf does not support access from a single host specified by hostname
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Mar 27 08:30:01 1997
>Originator:     rodgers@nlm.nih.gov
>Organization:
apache
>Release:        1.2b7
>Environment:
Solaris 2.5.1, gcc 2.7.2
>Description:
The conf/access.conf file is used to configure access to the server.
Although the online manual suggests that a series of configuration
commands of the form:
   deny from all
   allow from ugweb.cs.ualberta.ca
should be possible, it does not work as described (access is denied to host
ugweb), whereas:
   deny from all
   allow from .cs.ualberta.ca
does allow access to host ugweb, as well as all of its peers in the domain
cs.ualberta.ca.  Preceding the hostname in the first example with "." does
not function as a work-around.  Either the document should be clarified, or
(preferably) the code modified.
>How-To-Repeat:
The above example should suffice
>Fix:
Hack the access code
>Audit-Trail:
>Unformatted:



Re: config/270: access.conf does not support access from a single host specified by hostname

Posted by Marc Slemko <ma...@znep.com>.
Try replacing ugweb.cs.ualberta.ca with gwynne.cs.ualberta.ca.  The
reverse DNS for ugweb points to gwynne because gywynne is the real machine
name.

If you look in the access log, you should see the accesses coming from
gwynne and not ugweb.  

If this doesn't work, send me the output from the access log for when it
is denied.

good pick of hosts; gwynne is sitting in the room next to me as I
write... <g>

On Thu, 27 Mar 1997, R. P. C. Rodgers wrote:

> 
> >Number:         270
> >Category:       config
> >Synopsis:       access.conf does not support access from a single host specified by hostname
> >Confidential:   no
> >Severity:       non-critical
> >Priority:       medium
> >Responsible:    apache (Apache HTTP Project)
> >State:          open
> >Class:          sw-bug
> >Submitter-Id:   apache
> >Arrival-Date:   Thu Mar 27 08:30:01 1997
> >Originator:     rodgers@nlm.nih.gov
> >Organization:
> apache
> >Release:        1.2b7
> >Environment:
> Solaris 2.5.1, gcc 2.7.2
> >Description:
> The conf/access.conf file is used to configure access to the server.
> Although the online manual suggests that a series of configuration
> commands of the form:
>    deny from all
>    allow from ugweb.cs.ualberta.ca
> should be possible, it does not work as described (access is denied to host
> ugweb), whereas:
>    deny from all
>    allow from .cs.ualberta.ca
> does allow access to host ugweb, as well as all of its peers in the domain
> cs.ualberta.ca.  Preceding the hostname in the first example with "." does
> not function as a work-around.  Either the document should be clarified, or
> (preferably) the code modified.
> >How-To-Repeat:
> The above example should suffice
> >Fix:
> Hack the access code
> >Audit-Trail:
> >Unformatted:
> 
>