Closed przygienda closed 3 years ago
Is it sufficient to add mode
option that specifies the umask value of the created files? ( https://doc.rust-lang.org/std/os/unix/fs/trait.OpenOptionsExt.html#tymethod.mode ).
I do think so ... Even better solution
On Sun, Sep 30, 2018 at 2:53 AM Takeru Ohta notifications@github.com wrote:
Is it sufficient to add mode option that specifies the umask value of the created files? ( https://doc.rust-lang.org/std/os/unix/fs/trait.OpenOptionsExt.html#tymethod.mode ).
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sile/sloggers/issues/17#issuecomment-425708732, or mute the thread https://github.com/notifications/unsubscribe-auth/ABo0C_crybcaVqvlx86_GYQLuNySwN2kks5ugJSmgaJpZM4W3Byx .
It's often desirable on secure systems to restrict whether a log file is world-readable. It would be good to add something small to API sayiong "remove world readable when generating the log file" no matter what the umask says ...