Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (hermes.apache.org: domain of mawic@gmx.de designates
 213.165.64.20 as permitted sender)
Message-ID: <423B3587.3070505@gmx.de>
Date: Fri, 18 Mar 2005 21:09:43 +0100
From: Markus Wichitill <mawic@gmx.de>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Jonathan Vanasco <jvanasco@mastersofbranding.com>
CC: apreq-dev@httpd.apache.org
Subject: Re: Upload Question
References: <5b8e4dde7d68b3a65de106863f30776e@mastersofbranding.com>
In-Reply-To: <5b8e4dde7d68b3a65de106863f30776e@mastersofbranding.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jonathan Vanasco wrote:
> I've noticed that i can't seem to affect the umask of uploaded files 
> that i $upload->link()
> 
> I *think* this is because I am changing the umask in mod_perl, and the 
> link is happening in libaprq, so nothing I do in modperl affects libaprq 
> -- and that the only way for me to change the umask used to create the 
> files via link would be to change the umask for the apache user (or call 
> a chmod in modperl after the link).
> 
>  i'd like to eliminate the chmod call if possible, but it does work so I 
> can live with it
> 
> can anyone confirm this or yell at me for being stupid?

I stumbled over that a few years ago, too. apreq 1.x has the file 
permissions hardcoded to 0600 and ignores the user's umask. Just keep the 
"chmod 0666 & ~umask(), $file" or whatever.