File: allowtrusteddomains.xml

package info (click to toggle)
samba 2%3A3.5.6~dfsg-3squeeze13
  • links: PTS, VCS
  • area: main
  • in suites: squeeze-lts
  • size: 146,276 kB
  • ctags: 140,269
  • sloc: ansic: 1,269,622; xml: 115,137; perl: 26,869; python: 13,704; sh: 13,575; makefile: 4,936; asm: 3,281; cpp: 2,225; yacc: 1,930; exp: 1,784; ada: 1,681; pascal: 1,089; cs: 879; lex: 561; awk: 540; csh: 58; sed: 45; php: 6
file content (26 lines) | stat: -rw-r--r-- 1,272 bytes parent folder | download | duplicates (9)
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
<samba:parameter name="allow trusted domains"
                 context="G"
				 type="boolean"
                 advanced="1" developer="1"
		 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
    <para>
    This option only takes effect when the <smbconfoption name="security"/> option is set to 
    <constant>server</constant>, <constant>domain</constant> or <constant>ads</constant>.  
    If it is set to no, then attempts to connect to a resource from 
    a domain or workgroup other than the one which smbd is running 
    in will fail, even if that domain is trusted by the remote server 
    doing the authentication.</para>
		
    <para>This is useful if you only want your Samba server to 
    serve resources to users in the domain it is a member of. As 
    an example, suppose that there are two domains DOMA and DOMB.  DOMB 
    is trusted by DOMA, which contains the Samba server.  Under normal 
    circumstances, a user with an account in DOMB can then access the 
    resources of a UNIX account with the same account name on the 
    Samba server even if they do not have an account in DOMA.  This 
    can make implementing a security boundary difficult.</para>
</description>

<value type="default">yes</value>
</samba:parameter>