summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/security/restrictanonymous.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/docbook/smbdotconf/security/restrictanonymous.xml')
-rw-r--r--docs/docbook/smbdotconf/security/restrictanonymous.xml35
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/docbook/smbdotconf/security/restrictanonymous.xml b/docs/docbook/smbdotconf/security/restrictanonymous.xml
new file mode 100644
index 0000000000..25d2ba0df6
--- /dev/null
+++ b/docs/docbook/smbdotconf/security/restrictanonymous.xml
@@ -0,0 +1,35 @@
+<samba:parameter name="restrict anonymous"
+ context="G"
+ advanced="1" developer="1"
+ xmlns:samba="http://samba.org/common">
+<listitem>
+ <para>The setting of this parameter determines whether user and
+ group list information is returned for an anonymous connection.
+ and mirrors the effects of the
+ <constant>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\RestrictAnonymous</constant> registry key in Windows
+ 2000 and Windows NT. When set to 0, user and group list
+ information is returned to anyone who asks. When set
+ to 1, only an authenticated user can retrive user and
+ group list information. For the value 2, supported by
+ Windows 2000/XP and Samba, no anonymous connections are allowed at
+ all. This can break third party and Microsoft
+ applications which expect to be allowed to perform
+ operations anonymously.</para>
+
+ <para>
+ The security advantage of using restrict anonymous = 1 is dubious,
+ as user and group list information can be obtained using other
+ means.
+ </para>
+
+ <note>
+ <para>
+ The security advantage of using restrict anonymous = 2 is removed
+ by setting <link linkend="GUESTOK"><parameter moreinfo="none">guest
+ ok</parameter> = yes</link> on any share.
+ </para>
+ </note>
+
+ <para>Default: <command moreinfo="none">restrict anonymous = 0</command></para>
+</listitem>
+</samba:parameter>