Fix to allow setting of NULL DACL/SACL
commitc8dfc2dbfdbc344a68f4f11f5935ff42b5795d18
authorSteven Danneman <steven.danneman@isilon.com>
Mon, 24 Nov 2008 20:05:09 +0000 (24 12:05 -0800)
committerKarolin Seeger <kseeger@samba.org>
Wed, 26 Nov 2008 09:13:44 +0000 (26 10:13 +0100)
tree7a8e0d5eae536f770309be0107eb2dfeefe0a474
parentb16eb9433c6d6560284ca52e48e58a4b581a2213
Fix to allow setting of NULL DACL/SACL

This is a modification of Jeremy's 7522ef15aca2429ef57c75d8297dd8121e79c9da
commit.

If no DACL/SACL is present in the packet, the SEC_INFO field should still be
passed down as is to the VFS layer to signal the creation of a NULL DACL/SACL.

As seen in metze RAW-ACL test_nttrans_create_null_dacl(), a NULL DACL is set
regardless of the SEC_DESC_DACL_PRESENT bit being set.
(cherry picked from commit fc064837fbf84726ad66b16ef6e1f8c67d47a1fe)
source/smbd/nttrans.c