Re: general/3920: Umask is inherited by Apache CGIs
[In order for any reply to be added to the PR database, ] [you need to include [EMAIL PROTECTED] in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ] Synopsis: Umask is inherited by Apache CGIs State-Changed-From-To: open-closed State-Changed-By: dgaudet State-Changed-When: Tue Apr 20 16:28:10 PDT 1999 State-Changed-Why: I suggest editing your apachectl script to change the umask. There is no one setting which we could default to which makes sense for all systems. For some, 022 is right, for others 002 is right. If you've got admins using different umasks I think you've got other problems... what happens if they create files as root? Dean
general/3920: Umask is inherited by Apache CGIs
Number: 3920 Category: general Synopsis: Umask is inherited by Apache CGIs Confidential: no Severity: non-critical Priority: medium Responsible:apache State: open Class: change-request Submitter-Id: apache Arrival-Date: Thu Feb 18 13:50:01 PST 1999 Last-Modified: Originator: [EMAIL PROTECTED] Organization: apache Release:1.3.4 Environment: All Description: When different administrators start Apache, sometimes their umasks are abnormally restrictive and adversely affect CGIs such as FrontPage. It would be nice to have apachectl hard-set the umask, or to create a Umask directive for Apache. How-To-Repeat: Set umask to 077. Start Apache. CGIs will inherit umask. Fix: The Umask directive I think would be the cleanest way. Audit-Trail: Unformatted: [In order for any reply to be added to the PR database, ] [you need to include [EMAIL PROTECTED] in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
