[30968] in bugtraq

home help back first fref pref prev next nref lref last post

Re: Apache 1.3.27 mod_proxy security issue

daemon@ATHENA.MIT.EDU (Joshua Slive)
Wed Jul 30 14:54:24 2003

Date: Tue, 29 Jul 2003 17:01:06 -0400 (=?ISO-8859-1?Q?Est_=28heure_d'=E9t=E9=29?=)
From: Joshua Slive <joshua@slive.ca>
To: docs@httpd.apache.org
In-Reply-To: <5.2.0.9.2.20030729150030.02c76008@pop3.rowe-clan.net>
Message-ID: <Pine.WNT.4.55.0307291654310.1396@Poste3947.hec.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 29 Jul 2003, William A. Rowe, Jr. wrote:
> At 12:31 PM 7/23/2003, Greg A. Woods wrote:
>
> >I don't know how clients are matched against domains in ACL statements
> >such as the above in Apache, but I will note that it is NEVER safe to
> >rely on the Reverse DNS alone to implement ACLs that affect the ability
> >of a random remote client system.
>
> On this point, too, it would be valuable to provide an example subnet as
> a preferable alternative to reverse DNS queries.  That change has not been
> made yet - but is referred to our documentation project.

Apache does double-reverse lookups to assure that nothing too funky is
going on, so using dns names is relatively safe.  It is still better to
use an IP subnet for performance reasons, but the hostname may be easier
to understand as an example.

Joshua.

home help back first fref pref prev next nref lref last post