From 59462f2e0102481bb9ac8f86e883a6de99259449 Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Mon, 17 Jun 2013 17:25:41 -0700 Subject: winbindd and nmbd don't set their umask to zero on startup like smbd does. Fix this - we already control tightly what permissions are on the files we create. Ensure we don't get surprised. Signed-off-by: Jeremy Allison Reviewed-by: Michael Adam Autobuild-User(master): Michael Adam Autobuild-Date(master): Thu Jun 27 02:02:24 CEST 2013 on sn-devel-104 --- source3/winbindd/winbindd.c | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'source3/winbindd') diff --git a/source3/winbindd/winbindd.c b/source3/winbindd/winbindd.c index 141ca5c7c5..953e208e2a 100644 --- a/source3/winbindd/winbindd.c +++ b/source3/winbindd/winbindd.c @@ -1336,6 +1336,12 @@ int main(int argc, char **argv, char **envp) talloc_enable_null_tracking(); frame = talloc_stackframe(); + /* + * We want total control over the permissions on created files, + * so set our umask to 0. + */ + umask(0); + setup_logging("winbindd", DEBUG_DEFAULT_STDOUT); /* glibc (?) likes to print "User defined signal 1" and exit if a -- cgit