Bug 47435 - mod_authz_host does reading of /etc/hosts on each request
Summary: mod_authz_host does reading of /etc/hosts on each request
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_auth (show other bugs)
Version: 2.2.11
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2009-06-26 05:58 UTC by astle
Modified: 2018-11-07 21:08 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description astle 2009-06-26 05:58:30 UTC
It looks to me like that config like so:

<Directory /my/dir>
  Order deny,allow
  Deny  from    all

  Allow from    127.0.0.1
</Directory>

causes apache to read /etc/hosts on every request in the specified directory.

I didn't expect that IP-address-based ACLs would require a "double reverse" lookup (as is very nicely documented for hostname-based ACLs).

Two notes about bugzilla itself:

* I think this is specific to mod_authz_host but I don't see that in the component list.

* Was not clear to me which is the highest priority P1 or P5.  I think this should probably be the lowest or 2nd lowest priority.  A note on priority here:

https://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html

would help.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:59 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.