A few more little fixes, a few more edits, a bit lost here, and a lot gained there! :)

[vlendec/samba-autobuild/.git] / docs / docbook / projdoc / ServerType.xml

diff --git a/docs/docbook/projdoc/ServerType.xml b/docs/docbook/projdoc/ServerType.xml
index 91f0da9d8c449715725826d850420dd52e7ed270..13377b1d5acc0c1d8509f396a4660cc7d1a72f8f 100644 (file)
--- a/docs/docbook/projdoc/ServerType.xml
+++ b/docs/docbook/projdoc/ServerType.xml
@@ -12,7 +12,7 @@ This chapter provides information regarding the types of server that Samba may b
 configured to be. A Microsoft network administrator who wishes to migrate to or to
 use Samba will want to know what within a Samba context, terms familiar to MS Windows
 adminstrator mean. This means that it is essential also to define how critical security
-contexts function BEFORE we get into the details of how to configure the server itself.
+modes function BEFORE we get into the details of how to configure the server itself.
 </para>
 
 <para>
@@ -27,7 +27,7 @@ features and benefits. These may be for or against Samba.
 </para>
 
 <sect1>
-<title>Samba Features and Benefits</title>
+<title>Features and Benefits</title>
 
 <para>
 Two men were walking down a dusty road, when one suddenly kicked up a small red stone. It
@@ -131,6 +131,17 @@ mode as well as how to configure MS Windows clients for each mode will significa
 reduce user complaints and administrator heartache.
 </para>
 
+<para>
+There are in the SMB/CIFS networking world only two types of security: <emphasis>USER Level</emphasis>
+and <emphasis>SHARE Level</emphasis>. We refer to these collectively as <emphasis>security levels</emphasis>. In implementing these two <emphasis>security levels</emphasis> samba provides flexibilities
+that are not available with Microsoft Windows NT4 / 200x servers. Samba knows of fice (5)
+ways that allow the security levels to be implemented. In actual fact, Samba implements
+<emphasis>SHARE Levl</emphasis> security only one way, but has for ways of implementing
+<emphasis>USER Level</emphasis> security. Collectively, we call the samba implementations
+<emphasis>Security Modes</emphasis>. These are: <emphasis>SHARE, USER, DOMAIN, ADS, and SERVER</emphasis>
+modes. They are documented in this chapter.
+</para>
+
 <para>
 A SMB server tells the client at startup what <emphasis>security level</emphasis>
 it is running. There are two options <emphasis>share level</emphasis> and
@@ -244,7 +255,7 @@ with share mode security servers. You are strongly discouraged from use of this
 </sect2>
 
 <sect2>
-<title>Domain Level Security</title>
+<title>Domain Security Mode (User Level Security)</title>
 
 <para>
 When samba is operating in <emphasis>security = domain</emphasis> mode this means that
@@ -313,12 +324,12 @@ in this HOWTO collection.
 </sect2>
 
 <sect2>
-<title>ADS Level Security</title>
+<title>ADS Security Mode (User Level Security)</title>
 
 <para>
 Samba-2.2.x could join and Active Directory domain so long as the Active Directory domain
 controller is configured for mixed mode operation, and is running NetBIOS over TCP/IP. MS
-Windows 2000 and later can be configured to run without NEtBIOS over TCP/IP, instead it
+Windows 2000 and later can be configured to run without NetBIOS over TCP/IP, instead it
 can run SMB natively over TCP/IP.
 </para>
 
@@ -334,7 +345,7 @@ to be a native Active Directory member server.
 
 <para>
 <programlisting>
-       realm = your.kerberos.realm
+       realm = your.kerberos.REALM
        security = ADS
        encrypt passwords = Yes
 
@@ -353,7 +364,7 @@ regarding this configuration option.
 </sect2>
 
 <sect2>
-<title>Server Level Security</title>
+<title>Server Security (User Level Security)</title>
 
 <para>
 Server level security is a left over from the time when Samba was not capable of acting