Chapter 3. Server Types and Security Modes
Chapter 3. Server Types and Security Modes Prev Part II. Server Configuration Basics Next Chapter 3. Server Types and Security Modes Andrew Samba Team Tridgell Samba Team < tridge@samba.org > Jelmer R. The Samba Team Vernooij The Samba Team < jelmer@samba.org > John H. Samba Team Terpstra Samba Team < jht@samba.org > Table of Contents Features and Benefits Server Types Samba Security Modes User Level Security Share-Level Security Domain Security Mode (User-Level Security) ADS Security Mode (User-Level Security) Server Security (User Level Security) Password Checking Common Errors What Makes Samba a Server?
What Makes Samba a Domain Controller? What Makes Samba a Domain Member? Constantly Losing Connections to Password Server Stand-alone Server is converted to Domain Controller Now User accounts don't work This chapter provides information regarding the types of server that Samba may be configured to be. A Microsoft network administrator who wishes to migrate to or use Samba will want to know the meaning, within a Samba context, of terms familiar to the MS Windows administrator.
This means that it is essential also to define how critical security modes function before we get into the details of how to configure the server itself. This chapter provides an overview of the security modes of which Samba is capable and how they relate to MS Windows servers and clients. A question often asked is, “ Why would I want to use Samba? ” Most chapters contain a section that highlights features and benefits.
We hope that the information provided will help to answer this question. Be warned though, we want to be fair and reasonable, so not all features are positive toward Samba. The benefit may be on the side of our competition. Features and Benefits Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It hurt his toe and lodged in his sandal. He took the stone out and cursed it with a passion and fury befitting his anguish.
The other looked at the stone and said, “ This is a garnet. I can turn that into a precious gem and some day it will make a princess very happy! ” The moral of this tale: Two men, two very different perspectives regarding the same stone. Like it or not, Samba is like that stone. Treat it the right way and it can bring great pleasure, but if you are forced to use it and have no time for its secrets, then it can be a source of discomfort.
Samba started out as a project that sought to provide interoperability for MS Windows 3.x clients with a UNIX server. It has grown up a lot since its humble beginnings and now provides features and functionality fit for large-scale deployment. It also has some warts. In sections like this one, we tell of both. So, what are the benefits of the features mentioned in this chapter? Samba-3 can replace an MS Windows NT4 domain controller.
Samba-3 offers excellent interoperability with MS Windows NT4-style domains as well as natively with Microsoft Active Directory domains. Samba-3 permits full NT4-style interdomain trusts. Samba has security modes that permit more flexible authentication than is possible with MS Windows NT4 domain controllers. Samba-3 permits use of multiple concurrent account database backends. (Encrypted passwords that are stored in the account database are in formats that are unique to Windows networking).
The account database backends can be distributed and replicated using multiple methods. This gives Samba-3 greater flexibility than MS Windows NT4 and in many cases a significantly higher utility than Active Directory domains with MS Windows 200x. Server Types Administrators of Microsoft networks often refer to three different types of servers: Domain Controller Primary Domain Controller (PDC) Backup Domain Controller (BDC) ADS Domain Controller Domain Member Server Active Directory Domain Server NT4 Style Domain Domain Server Standalone Server The chapters covering domain control ( Domain Control ), backup domain control ( Backup Domain Control ), and domain membership ( Domain Membership ) provide pertinent information regarding Samba configuration for each of these server roles.
You are strongly encouraged to become intimately familiar with these chapters because they lay the foundation for deployment of Samba domain security. A Standalone server is autonomous in respect of the source of its account backend. Refer to Standalone Servers to gain a wider appreciation of what is meant by a server being configured as a standalone server. Samba Security Modes In this section, the function and purpose of Samba's security modes are described.
An accurate understanding of how Samba implements each security mode as well as how to configure MS Windows clients for each mode will significantly reduce user complaints and administrator heartache. Microsoft Windows networking uses a protocol that was originally called the Server Message Block (SMB) protocol. Since some time around 1996 the protocol has been better known as the Common Internet Filesystem (CIFS) protocol.
In the SMB/CIFS networking world, there are only two types of security: user-level and share level . We refer to these collectively as security levels . In implementing these two security levels, Samba provides flexibilities that are not available with MS Windows NT4/200x servers. In fact, Samba implements share-level security only one way, but has four ways of implementing user-level security. Collectively, we call the Samba implementations of the security levels security modes .
They are known as share , user , domain , ADS , and server modes. They are documented in this chapter. An SMB server informs the client, at the time of a session setup, the security level the server is running. There are two options: share-level and user-level. Which of these two the client receives affects the way the client then tries to authenticate itself. It does not directly affect (to any great extent) the way the Samba server does security.
This may sound strange, but it fits in with the client/server approach of SMB. In SMB everything is initiated and controlled by the client, and the server can only tell the client what is available and whether an action is allowed. The term client refers to all agents whether it is a Windows workstation, a Windows server, another Samba server, or any vanilla SMB or CIFS client application (e.g., smbclient ) that make use of services provided by an SMB/CIFS server.
User Level Security We describe user-level security first because its simpler. In user-level security, the client sends a session setup request directly following protocol negotiation. This request provides a username and password. The server can either accept or reject that username/password combination. At this stage the server has no idea what share the client will eventually try to connect to, so it can't base the accept/reject on anything other than: the username/password. the name of the client machine.
If the server accepts the username/password credentials, the client expects to be able to mount shares (using a tree connection ) without further specifying a password. It expects that all access rights will be as the username/password credentials set that was specified in the initial session setup . It is also possible for a client to send multiple session setup requests. When the server responds, it gives the client a uid to use as an authentication tag for that username/password.
The client can maintain multiple authentication contexts in this way (WinDD is an example of an application that does this). Windows networking user account names are case-insensitive, meaning that upper-case and lower-case characters in the account name are considered equivalent. They are said to be case-preserving, but not case significant. Windows and LanManager systems previous to Windows NT version 3.10 have case-insensitive passwords that were not necessarily case-preserving.
All Windows NT family systems treat passwords as case-p
The rest of this page is on the live site.