On Sat, Jul 30, 2016 at 4:50 AM, kpcyrd <kpc...@rxv.cc> wrote: > So, upstream just closed the issue I created with 'Works as Designed' > blaming the default umask for the bug and that specifying file > permissions for files created by mongodb is not something mongodb should > do. > > https://jira.mongodb.org/browse/SERVER-25335#comment-1342085 > > The bug is locked, what do I do now? You mean what to do with upstream? I guess nothing. Probably I can fix this myself. While this is a real issue, I somewhat agree with upstream. Being a system administrator for long time, I know as others should know: - don't run sensitive services on a machine which can be accessed by untrusted users, - even on your regular box set your $HOME to 0700 and your umask to 0077. In short, always expect the worst case and be prepared.
Regards, Laszlo/GCS
