On Sun, Nov 11, 2012 at 10:35:46PM +0100, Stefan Klinger wrote: > Yes, I'm aware of that. On the other hand: The current behavior seems > insane to me, unless there would be a good reason for by default > changing the umask to a less secure setting, but then that should be > documented. > > I agree with your objection though. To avoid that kind of trouble, I'd > suggest a stepwise change: > > * For the next release, make run-parts issue a warning that it changes > the umask, and that this behavior is going to change in the future. > Suppress the warning if the user sets the umask with -u. > > * For the following release, change run-parts to not tamper with the > umask anymore, and warn about the new situation, unless -u is given. > > * Finally remove the warning. > > Would that be of any use?
Let's solicit debian-devel's thoughts and opinions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
