diff options
Diffstat (limited to 'docs-xml/smbdotconf/security')
| -rw-r--r-- | docs-xml/smbdotconf/security/clientlanmanauth.xml | 2 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/clientsigning.xml | 3 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/lanmanauth.xml | 2 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/passwordserver.xml | 2 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/security.xml | 6 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/serverschannel.xml | 2 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/serversigning.xml | 3 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/smbencrypt.xml | 3 | ||||
| -rw-r--r-- | docs-xml/smbdotconf/security/updateencrypted.xml | 4 |
9 files changed, 12 insertions, 15 deletions
diff --git a/docs-xml/smbdotconf/security/clientlanmanauth.xml b/docs-xml/smbdotconf/security/clientlanmanauth.xml index 5266fef6a24..967eacf85bb 100644 --- a/docs-xml/smbdotconf/security/clientlanmanauth.xml +++ b/docs-xml/smbdotconf/security/clientlanmanauth.xml @@ -11,7 +11,7 @@ password hashes (e.g. Windows NT/2000, Samba, etc... but not Windows 95/98) will be able to be connected from the Samba client.</para> - <para>The LANMAN encrypted response is easily broken, due to it's + <para>The LANMAN encrypted response is easily broken, due to its case-insensitive nature, and the choice of algorithm. Clients without Windows 95/98 servers are advised to disable this option. </para> diff --git a/docs-xml/smbdotconf/security/clientsigning.xml b/docs-xml/smbdotconf/security/clientsigning.xml index bf37cbb8746..c657e057118 100644 --- a/docs-xml/smbdotconf/security/clientsigning.xml +++ b/docs-xml/smbdotconf/security/clientsigning.xml @@ -4,8 +4,7 @@ basic="1" xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> <description> - <para>This controls whether the client offers or requires - the server it talks to to use SMB signing. Possible values + <para>This controls whether the client is allowed or required to use SMB signing. Possible values are <emphasis>auto</emphasis>, <emphasis>mandatory</emphasis> and <emphasis>disabled</emphasis>. </para> diff --git a/docs-xml/smbdotconf/security/lanmanauth.xml b/docs-xml/smbdotconf/security/lanmanauth.xml index 341952205f6..4e68c5e03aa 100644 --- a/docs-xml/smbdotconf/security/lanmanauth.xml +++ b/docs-xml/smbdotconf/security/lanmanauth.xml @@ -12,7 +12,7 @@ Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.</para> - <para>The LANMAN encrypted response is easily broken, due to it's + <para>The LANMAN encrypted response is easily broken, due to its case-insensitive nature, and the choice of algorithm. Servers without Windows 95/98/ME or MS DOS clients are advised to disable this option. </para> diff --git a/docs-xml/smbdotconf/security/passwordserver.xml b/docs-xml/smbdotconf/security/passwordserver.xml index 0da247d27d5..0e92af9ebae 100644 --- a/docs-xml/smbdotconf/security/passwordserver.xml +++ b/docs-xml/smbdotconf/security/passwordserver.xml @@ -7,7 +7,7 @@ <para>By specifying the name of another SMB server or Active Directory domain controller with this option, and using <command moreinfo="none">security = [ads|domain|server]</command> - it is possible to get Samba to + it is possible to get Samba to do all its username/password validation using a specific remote server.</para> <para>This option sets the name or IP address of the password server to use. diff --git a/docs-xml/smbdotconf/security/security.xml b/docs-xml/smbdotconf/security/security.xml index 3ad5175712e..514ea54e0ff 100644 --- a/docs-xml/smbdotconf/security/security.xml +++ b/docs-xml/smbdotconf/security/security.xml @@ -47,7 +47,7 @@ want to mainly setup shares without a password (guest shares). This is commonly used for a shared printer server. It is more difficult to setup guest shares with <command moreinfo="none">security = user</command>, see - the <smbconfoption name="map to guest"/>parameter for details.</para> + the <smbconfoption name="map to guest"/> parameter for details.</para> <para>It is possible to use <command moreinfo="none">smbd</command> in a <emphasis> hybrid mode</emphasis> where it is offers both user and share @@ -58,7 +58,7 @@ <para><anchor id="SECURITYEQUALSSHARE"/><emphasis>SECURITY = SHARE</emphasis></para> - <para>When clients connect to a share level security server they + <para>When clients connect to a share level security server, they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with @@ -211,7 +211,7 @@ </para></note> <note><para>From the client's point of - view <command moreinfo="none">security = server</command> is the + view, <command moreinfo="none">security = server</command> is the same as <command moreinfo="none">security = user</command>. It only affects how the server deals with the authentication, it does not in any way affect what the client sees.</para></note> diff --git a/docs-xml/smbdotconf/security/serverschannel.xml b/docs-xml/smbdotconf/security/serverschannel.xml index 6317448fb62..655463576f3 100644 --- a/docs-xml/smbdotconf/security/serverschannel.xml +++ b/docs-xml/smbdotconf/security/serverschannel.xml @@ -13,7 +13,7 @@ </para> <para> - Please note that with this set to <literal>no</literal> you will have to apply the WindowsXP + Please note that with this set to <literal>no</literal>, you will have to apply the WindowsXP <filename>WinXP_SignOrSeal.reg</filename> registry patch found in the docs/registry subdirectory of the Samba distribution tarball. </para> </description> diff --git a/docs-xml/smbdotconf/security/serversigning.xml b/docs-xml/smbdotconf/security/serversigning.xml index f2f56295861..ea21a2c6f64 100644 --- a/docs-xml/smbdotconf/security/serversigning.xml +++ b/docs-xml/smbdotconf/security/serversigning.xml @@ -5,8 +5,7 @@ xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> <description> - <para>This controls whether the server offers or requires - the client it talks to to use SMB signing. Possible values + <para>This controls whether the client is allowed or required to use SMB signing. Possible values are <emphasis>auto</emphasis>, <emphasis>mandatory</emphasis> and <emphasis>disabled</emphasis>. </para> diff --git a/docs-xml/smbdotconf/security/smbencrypt.xml b/docs-xml/smbdotconf/security/smbencrypt.xml index eb91ce51fa3..d5561669536 100644 --- a/docs-xml/smbdotconf/security/smbencrypt.xml +++ b/docs-xml/smbdotconf/security/smbencrypt.xml @@ -16,8 +16,7 @@ and MacOS/X clients. Windows clients do not support this feature. </para> - <para>This controls whether the server offers or requires - the client it talks to to use SMB encryption. Possible values + <para>This controls whether the remote client is allowed or required to use SMB encryption. Possible values are <emphasis>auto</emphasis>, <emphasis>mandatory</emphasis> and <emphasis>disabled</emphasis>. This may be set on a per-share basis, but clients may chose to encrypt the entire session, not diff --git a/docs-xml/smbdotconf/security/updateencrypted.xml b/docs-xml/smbdotconf/security/updateencrypted.xml index da493665cf2..eb54ed9bab6 100644 --- a/docs-xml/smbdotconf/security/updateencrypted.xml +++ b/docs-xml/smbdotconf/security/updateencrypted.xml @@ -9,7 +9,7 @@ This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on. This option allows a site to migrate from plaintext password authentication (users authenticate with plaintext password over the - wire, and are checked against a UNIX account atabase) to encrypted password authentication (the SMB + wire, and are checked against a UNIX account database) to encrypted password authentication (the SMB challenge/response authentication mechanism) without forcing all users to re-enter their passwords via smbpasswd at the time the change is made. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period. Once all users have encrypted representations of their passwords @@ -24,7 +24,7 @@ </para> <para> - Note that even when this parameter is set a user authenticating to <command moreinfo="none">smbd</command> + Note that even when this parameter is set, a user authenticating to <command moreinfo="none">smbd</command> must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd) passwords. </para> |