From 8daa83a594a2e98f39d764422bfbdbc62c9efd44 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Fri, 19 Apr 2024 19:20:00 +0200
Subject: Adding upstream version 2:4.20.0+dfsg.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 docs-xml/smbdotconf/security/inheritowner.xml | 58 +++++++++++++++++++++++++++
 1 file changed, 58 insertions(+)
 create mode 100644 docs-xml/smbdotconf/security/inheritowner.xml

(limited to 'docs-xml/smbdotconf/security/inheritowner.xml')

diff --git a/docs-xml/smbdotconf/security/inheritowner.xml b/docs-xml/smbdotconf/security/inheritowner.xml
new file mode 100644
index 0000000..c081e56
--- /dev/null
+++ b/docs-xml/smbdotconf/security/inheritowner.xml
@@ -0,0 +1,58 @@
+<samba:parameter name="inherit owner"
+                 context="S"
+                 type="enum"
+		 enumlist="enum_inherit_owner_vals"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>The ownership of new files and directories 
+	is normally governed by effective uid of the connected user.
+	This option allows the Samba administrator to specify that
+	the ownership for new files and directories should be controlled
+	by the ownership of the parent directory.</para>
+
+	<para>Valid options are:</para>
+	<itemizedlist>
+	<listitem><para><constant>no</constant> -
+	Both the Windows (SID) owner and the UNIX (uid) owner of the file are
+	governed by the identity of the user that created the file.
+	</para></listitem>
+
+	<listitem><para><constant>windows and unix</constant> -
+	The Windows (SID) owner and the UNIX (uid) owner of new files and
+	directories are set to the respective owner of the parent directory.
+	</para></listitem>
+
+	<listitem><para><constant>yes</constant> - a synonym for
+	<constant>windows and unix</constant>.
+	</para></listitem>
+
+	<listitem><para><constant>unix only</constant> -
+	Only the UNIX owner is set to the UNIX owner of the parent directory.
+	</para></listitem>
+	</itemizedlist>
+
+	<para>Common scenarios where this behavior is useful is in 
+	implementing drop-boxes, where users can create and edit files but
+	not delete them and ensuring that newly created files in a user's
+	roaming profile directory are actually owned by the user.</para>
+
+	<para>The <constant>unix only</constant> option effectively
+	breaks the tie between the Windows owner of a file and the
+	UNIX owner. As a logical consequence, in this mode,
+	setting the Windows owner of a file does not modify the UNIX
+	owner. Using this mode should typically be combined with a
+	backing store that can emulate the full NT ACL model without
+	affecting the POSIX permissions, such as the acl_xattr
+	VFS module, coupled with
+	<smbconfoption name="acl_xattr:ignore system acls">yes</smbconfoption>.
+	This can be used to emulate folder quotas, when files are
+	exposed only via SMB (without UNIX extensions).
+	The UNIX owner of a directory is locally set
+	and inherited by all subdirectories and files, and they all
+	consume the same quota.</para>
+</description>
+
+<related>inherit permissions</related>
+
+<value type="default">no</value>
+</samba:parameter>
-- 
cgit v1.2.3