summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/security/hostsequiv.xml
blob: 529f464a7b86b6db80f59ed363e7e9e8be222eef (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
<samba:parameter name="hosts equiv"
                 context="G"
				 type="string"
                 advanced="1" developer="1"
		 xmlns:samba="http://samba.org/common">
<description>
    <para>If this global parameter is a non-null string, 
    it specifies the name of a file to read for the names of hosts 
    and users who will be allowed access without specifying a password.
    </para>
		
    <para>This is not be confused with <link linkend="HOSTSALLOW">
    <parameter moreinfo="none">hosts allow</parameter></link> which is about hosts 
    access to services and is more useful for guest services. <parameter moreinfo="none">
    hosts equiv</parameter> may be useful for NT clients which will 
    not supply passwords to Samba.</para>

    <note><para>The use of <parameter moreinfo="none">hosts equiv
    </parameter> can be a major security hole. This is because you are 
    trusting the PC to supply the correct username. It is very easy to 
    get a PC to supply a false username. I recommend that the 
    <parameter moreinfo="none">hosts equiv</parameter> option be only used if you really 
    know what you are doing, or perhaps on a home network where you trust 
    your spouse and kids. And only if you <emphasis>really</emphasis> trust 
	them :-).</para></note>
</description>
		
<value type="default"><comment>no host equivalences</comment></value>
<value type="example">hosts equiv = /etc/hosts.equiv</value>
</samba:parameter>