Table of Contents
Advertisement
Chapter 14. Samba
the client. The server expects a password for each share, independent of the username. There
have been recent reports that Microsoft Windows clients have compatibility issues with
share-level security servers. Samba developers strongly discourage use of share-level security.
In
, the
smb.conf
security = share
[GLOBAL]
...
security = share
...
4.3. Domain Security Mode (User-Level Security)
In domain security mode, the Samba server has a machine account (domain security trust
account) and causes all authentication requests to be passed through to the domain controllers.
The Samba server is made into a domain member server by using the following directives in
:
smb.conf
[GLOBAL]
...
security = domain
workgroup = MARKETING
...
4.4. Active Directory Security Mode (User-Level Security)
If you have an Active Directory environment, it is possible to join the domain as a native Active
Directory member. Even if a security policy restricts the use of NT-compatible authentication
protocols, the Samba server can join an ADS using Kerberos. Samba in Active Directory
member mode can accept Kerberos tickets.
In
, the following directives make Samba an Active Directory member server:
smb.conf
[GLOBAL]
...
security = ADS
realm = EXAMPLE.COM
password server = kerberos.example.com
...
4.5. Server Security Mode (User-Level Security)
Server security mode was previously used when Samba was not capable of acting as a domain
member server.
262
directive that sets share-level security is:
Advertisement
Table of Contents
