The following reply was made to PR mod_include/1066; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Apache bugs database <[EMAIL PROTECTED]> Subject: RE: mod_include/1066: includesNOEXEC does not shut off "exec cmd" . . . (fwd) Date: Thu, 28 Aug 1997 11:25:56 -0600 (MDT) ---------- Forwarded message ---------- Date: Thu, 28 Aug 1997 12:13:17 -0500 From: "Bryan B. Campbell" <[EMAIL PROTECTED]> To: 'Marc Slemko' <[EMAIL PROTECTED]> Subject: RE: mod_include/1066: includesNOEXEC does not shut off "exec cmd" . . . My apologies . . . I was using improper directory directives in the access.conf. If you do not limit things consistently across all directories then exec cmd will plague you even if your root directories are set for includesNOEXEC. -----Original Message----- From: Marc Slemko [SMTP:[EMAIL PROTECTED] Sent: Wednesday, August 27, 1997 11:03 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: mod_include/1066: includesNOEXEC does not shut off "exec cmd" . . . Synopsis: includesNOEXEC does not shut off "exec cmd" . . . State-Changed-From-To: open-analyzed State-Changed-By: marc State-Changed-When: Wed Aug 27 21:02:28 PDT 1997 State-Changed-Why: And what URL are you trying to access? If it is something under /~fidelity/, then what does "echo ~fidelity" return? That is the path you have to use; /home may be a symlink, in which case your restriction would be for the wrong directory.
