s3: lib: messages: Don't use the result of sec_init() before calling sec_init().
commitd217375a87d49d65aeff9957d50046722b40e734
authorLutz Justen <ljusten@google.com>
Wed, 4 Apr 2018 16:50:12 +0000 (4 09:50 -0700)
committerKarolin Seeger <kseeger@samba.org>
Tue, 10 Apr 2018 07:38:08 +0000 (10 09:38 +0200)
treeaec89e781b4609d24b945d74d9b92ca663018954
parentc62c1c93f5712e7c3590eb9b9df9573300bd229a
s3: lib: messages: Don't use the result of sec_init() before calling sec_init().

Commit ad8c7171ba86e8a47d78b0c7329bb814e5a8871e accidently
moved sec_init() to the point after sec_initial_uid() is
called in the call to directory_create_or_exist_strict().
I missed this in the review (sorry). This works as root
as initial_uid/initial_gid are static (and so initialized
as zero) but doesn't work on ChromeOS as this code isn't
running as root.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=13368

Signed-off-by: Lutz Justen <ljusten@google.com>
Reviewed-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Andreas Schneider <asn@samba.org>
Autobuild-User(master): Jeremy Allison <jra@samba.org>
Autobuild-Date(master): Wed Apr  4 23:52:02 CEST 2018 on sn-devel-144

(cherry picked from commit e895b6cf4a7eb3d50d618a022be74db85975bf69)
source3/lib/messages.c