Michael Orlitzky wrote: > This is the right way to do it. The user/system already has UMASK set > to something generally acceptable. When you create a sensitive file, > you mask more permission bits, create the file, and then revert the > umask. After that, you leave everything alone.
Ok, thank you all for your comments. I implemented a minimal fix at #29093. People who'd like to see a warning issued in some circumstances or whatever are welcome to take over the ticket and make the improvements they find useful :-) -- Marc -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/r0palc%242g54%241%40ciao.gmane.io.
