- From: Eric-Olivier Lamey <
>
- To:
- Subject: [chef] Re: Re: Re: Is CHEF-686 back from the dead? (umask problem)
- Date: Mon, 14 Feb 2011 09:13:44 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=FtnlLEFJnoes5POMAtTs2Dcbg6fDOPJ5DULfziHgILOVm5UYqpwV7oEInzlRPpQTlh dXSapcQIczz5yjrV4jkPhyX8x90zg4PU0RtzSA2vP0tPTtRlNCdA/hw/PqfafwNuvmmt vXPvbyMHYJjP/Xod0nPuw8xKmS5RAtmNUOOpQ=
On Sat, Feb 12, 2011 at 8:04 PM, Daniel DeLeo
<
>
wrote:
>
Has anyone seen the same problem as I have? Do you have any log
>
file, cache or generated certificate which are world writable permission??
>
>
If I add
>
File.umask Chef::Config[:umask]
>
at the end of "config/init.rb" for chef-server-api and chef-server-webui,
>
the problem is fixed.
>
>
Thank you.
>
>
If you can reliably reproduce this behavior and you have a fix, please
>
reopen the ticket and include this information.
>
Thanks,
Hi,
I can reproduce the problem but I just noticed my fix was not good
enough. Some files are still created with the wrong rights.
I'll look into it and try to submit a patch.
Archive powered by MHonArc 2.6.16.