diff --git a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml index 8dbc007e4f3..2f3b568471f 100644 --- a/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml +++ b/docs/docbook/projdoc/Samba-BDC-HOWTO.sgml @@ -57,9 +57,9 @@ parameters in the [global]-section of the smb.conf have to be set: -workgroup = SAMBA -domain master = yes -domain logons = yes + workgroup = SAMBA + domain master = yes + domain logons = yes @@ -201,9 +201,9 @@ by setting -workgroup = samba -domain master = no -domain logons = yes + workgroup = samba + domain master = no + domain logons = yes diff --git a/docs/docbook/projdoc/ServerType.sgml b/docs/docbook/projdoc/ServerType.sgml index b38a9c097d7..7229a50201c 100644 --- a/docs/docbook/projdoc/ServerType.sgml +++ b/docs/docbook/projdoc/ServerType.sgml @@ -85,7 +85,7 @@ LDAP (from OpenLDAP), or Sun's iPlanet, of NetWare Directory Server, etc. Please refer to the section on Howto configure Samba as a Primary Domain Controller and for more information regarding how to create a domain machine account for a -domain member server as well as for information regading how to enable the samba +domain member server as well as for information regarding how to enable the samba domain member machine to join the domain and to be fully trusted by it. diff --git a/docs/docbook/projdoc/UNIX_INSTALL.sgml b/docs/docbook/projdoc/UNIX_INSTALL.sgml index 1019e524f71..3ad83c1f9df 100644 --- a/docs/docbook/projdoc/UNIX_INSTALL.sgml +++ b/docs/docbook/projdoc/UNIX_INSTALL.sgml @@ -88,13 +88,13 @@ SWAT is a web-based interface that helps you configure samba. SWAT might not be available in the samba package on your platform, - but in a seperate package. Please read the swat manpage + but in a separate package. Please read the swat manpage on compiling, installing and configuring swat from source. To launch SWAT just run your favorite web browser and point it at "http://localhost:901/". Replace localhost with the name of the computer you are running samba on if you - are running samba on a different computer then your browser. + are running samba on a different computer than your browser. Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your diff --git a/docs/docbook/projdoc/passdb.sgml b/docs/docbook/projdoc/passdb.sgml index 6f256daddd3..523a34603d9 100644 --- a/docs/docbook/projdoc/passdb.sgml +++ b/docs/docbook/projdoc/passdb.sgml @@ -238,8 +238,8 @@ data is stored at all. TDB Samba can also store the user data in a "TDB" (Trivial Database). Using this backend -doesn't require any additional configuration. This backend is recommended for new installations who -don't require LDAP. +doesn't require any additional configuration. This backend is recommended for new installations that +don not require LDAP. @@ -284,7 +284,7 @@ Two additional Samba resources which may prove to be helpful are -Introduction +Encrypted Password Database Traditionally, when configuring "encrypt @@ -327,7 +327,7 @@ API, and is still so named in the CVS trees). -There are a few points to stress about what the ldapsam +There are a few points to stress about that the ldapsam does not provide. The LDAP support referred to in the this documentation does not include: diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml index 3b5d054cad8..a729caf99ff 100644 --- a/docs/docbook/projdoc/samba-doc.sgml +++ b/docs/docbook/projdoc/samba-doc.sgml @@ -19,7 +19,7 @@ This book is a collection of HOWTOs added to Samba documentation over the years. -Samba is always under development, and so is it's documentation. This release of the +Samba is always under development, and so is its' documentation. This release of the documentation represents a major revision or layout as well as contents. The most recent version of this document can be found at http://www.samba.org/ @@ -35,8 +35,8 @@ or without their knowledge contributed to this update. The size and scope of thi project would not have been possible without significant community contribution. A not insignificant number of ideas for inclusion (if not content itself) has been obtained from a number of Unofficial HOWTOs - to each such author a big "Thank-you" is also offered. -Please keep publishing you Unofficial HOWTO's - they are a source of inspiration and -application knowledge that is most to be desired by may Samba users and administrators. +Please keep publishing your Unofficial HOWTO's - they are a source of inspiration and +application knowledge that is most to be desired by many Samba users and administrators. diff --git a/docs/docbook/projdoc/securing-samba.sgml b/docs/docbook/projdoc/securing-samba.sgml index e9e8c4f9f86..eedc7ba7253 100644 --- a/docs/docbook/projdoc/securing-samba.sgml +++ b/docs/docbook/projdoc/securing-samba.sgml @@ -2,6 +2,7 @@ &author.tridge; + &author.jht; 17 March 2003 @@ -36,8 +37,8 @@ might be: - hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24 - hosts deny = 0.0.0.0/0 + hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24 + hosts deny = 0.0.0.0/0 @@ -66,8 +67,8 @@ You can change this behaviour using options like the following: - interfaces = eth* lo - bind interfaces only = yes + interfaces = eth* lo + bind interfaces only = yes @@ -105,10 +106,10 @@ UDP ports to allow and block. Samba uses the following: -UDP/137 - used by nmbd -UDP/138 - used by nmbd -TCP/139 - used by smbd -TCP/445 - used by smbd + UDP/137 - used by nmbd + UDP/138 - used by nmbd + TCP/139 - used by smbd + TCP/445 - used by smbd @@ -135,9 +136,9 @@ To do that you could use: - [ipc$] - hosts allow = 192.168.115.0/24 127.0.0.1 - hosts deny = 0.0.0.0/0 + [ipc$] + hosts allow = 192.168.115.0/24 127.0.0.1 + hosts deny = 0.0.0.0/0 @@ -163,6 +164,32 @@ methods listed above for some reason. + +NTLMv2 Security + + +To configure NTLMv2 authentication the following registry keys are worth knowing about: + + + + + [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] + "lmcompatibilitylevel"=dword:00000003 + + 0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication, + use NTLMv2 session security if the server supports it. Domain + controllers accept LM, NTLM and NTLMv2 authentication. + + [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0] + "NtlmMinClientSec"=dword:00080000 + + 0x80000 - NTLMv2 session security. If either NtlmMinClientSec or + NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2 + session security is not negotiated. + + + + Upgrading Samba