On Wed, Jan 25, 2012 at 08:51:20AM +0100, Pierre Casenove wrote: > Hello, > I ran into an issue when I upgraded from SW 1.5 to SW 1.6: > - on my set up, root user has an umask of 0077 > - during setup, /etc/cobbler/settings is backuped and recreated... but > with permission set to root:root 600 > - Apache can't access the file until chmod 644 is performed
What is the error produced by Apache? > Please find attached a patch that simply calls chmod after cobbler > file has been created in spacewalk-setup perl script. > I couldn't test it in all cases so please review it carrefully. The problem I see with this approach to fixing the issue is that there are likely other situations when umask 0077 will simply produce unexpected results. So I wonder if spacewalk-setup should instead refuse to run if it detects something more restrictive than 0022? -- Jan Pazdziora Principal Software Engineer, Satellite Engineering, Red Hat _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
