2011/11/20 Clifford Heath <clifford.heath / gmail.com>:

> I think documentation is the wrong answer. The security defects are not caused
> by programs using mode 0666 - which they should do by default - but by the
> user having set their umask incorrectly. Ruby should not attempt to prevent this
> user error. There are situations where it's legal to create a file, but because of
> setuid mode on the directory, it's not possible for the program to chmod the new
> file. This problem can only be avoided by using the correct mode at creation.

Is there a situation that we needs world writable bit set by umask
configuration?

I'm considering to change 0600 to 0664.
-- 
Tanaka Akira