Return-Path: Delivered-To: apmail-apache-cvs-archive@apache.org Received: (qmail 45418 invoked by uid 500); 7 Mar 2001 23:44:47 -0000 Mailing-List: contact apache-cvs-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-cvs@apache.org Received: (qmail 45395 invoked by uid 500); 7 Mar 2001 23:44:44 -0000 Delivered-To: apmail-httpd-2.0-cvs@apache.org Date: Wed, 7 Mar 2001 15:44:12 -0800 (PST) From: X-Sender: To: Cc: Subject: Re: cvs commit: httpd-2.0 Makefile.in In-Reply-To: <20010307231356.16697.qmail@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > Modified: . Makefile.in > Log: > turn on setuid permissions when installing suexec I really dislike setting setuid from a Makefile. I would much rather make the admin set these permissions themselves. Just my opinion. Ryan > > Submitted by: Ken Coar > > Revision Changes Path > 1.59 +1 -0 httpd-2.0/Makefile.in > > Index: Makefile.in > =================================================================== > RCS file: /home/cvs/httpd-2.0/Makefile.in,v > retrieving revision 1.58 > retrieving revision 1.59 > diff -u -d -b -u -r1.58 -r1.59 > --- Makefile.in 2001/03/02 15:46:14 1.58 > +++ Makefile.in 2001/03/07 23:13:55 1.59 > @@ -119,6 +119,7 @@ > @if test -f $(builddir)/support/suexec; then \ > test -d $(sbindir) || $(MKINSTALLDIRS) $(sbindir); \ > cp -p $(srcdir)/support/suexec $(sbindir); \ > + chmod 4755 $(sbindir)/suexec; \ > fi > > suexec: > > > > > _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------