From 0c3c7fc205b7573bb6aecafb4eb5be6819b0fff8 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Tue, 28 Jun 2005 19:00:57 +0000 Subject: Update. (This used to be commit 69acfea203352d1b1d4d9bc72c41b01e7df9c2ec) --- docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml | 118 +++++++++++++++++++++---- 1 file changed, 99 insertions(+), 19 deletions(-) diff --git a/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml b/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml index 65b91dfa87..d1e601ff50 100644 --- a/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml +++ b/docs/Samba3-HOWTO/TOSHARG-upgrading-to-3.0.xml @@ -11,6 +11,9 @@ Upgrading from Samba-2.x to Samba-3.0.20 +Samba differences +changed parameters +simple guide This chapter deals exclusively with the differences between Samba-3.0.20 and Samba-2.2.8a. It points out where configuration parameters have changed, and provides a simple guide for the move from 2.2.x to 3.0.20. @@ -28,6 +31,8 @@ will use the smbpasswd database. +behavior approximately same +differing protocol So why say that behavior should be approximately the same as Samba-2.2.x? Because Samba-3.0.20 can negotiate new protocols, such as support for native Unicode, that may result in differing protocol code paths being taken. The new behavior under such circumstances is not @@ -36,6 +41,10 @@ preserved across the upgrade. +LDAP backend +database +pdbedit +Samba-3-compatible LDAP backend If the Samba-2.2.x system is using an LDAP backend, and there is no time to update the LDAP database, then make sure that ldapsam_compat is specified in the &smb.conf; file. For the rest, behavior should remain more or less the same. @@ -54,30 +63,37 @@ The major new features are: - + +ADS +LDAP/Kerberos Active Directory support. This release is able to join an ADS realm as a member server and authenticate users using LDAP/Kerberos. +Unicode +multibyte character sets Unicode support. Samba will now negotiate Unicode on the wire, and internally there is a much better infrastructure for multibyte and Unicode character sets. +authentication system New authentication system. The internal authentication system has been almost completely rewritten. Most of the changes are internal, but the new authoring system is also very configurable. +filename mangling New filename mangling system. The filename mangling system has been completely rewritten. An internal database now stores mangling maps persistently. +net command New net command. A new net command has been added. It is somewhat similar to the net command in Windows. Eventually, we plan to replace a bunch of other utilities (such as smbpasswd) @@ -85,34 +101,48 @@ The major new features are: +status32 codes Samba now negotiates NT-style status32 codes on the wire. This considerably improves error handling. +printer attributes publishing Better Windows 200x/XP printing support, including publishing printer attributes in Active Directory. +RPC modules +passdb backends +character sets New loadable RPC modules for passdb backends and character sets. +dual-daemon winbindd New default dual-daemon winbindd support for better performance. +migrating +maintaining ids +SID Support for migrating from a Windows NT 4.0 domain to a Samba domain and maintaining user, group, and domain SIDs. +trust relationships +domain controllers Support for establishing trust relationships with Windows NT 4.0 domain controllers. +Winbind architecture +LDAP directory +ID mapping Initial support for a distributed Winbind architecture using an LDAP directory for storing SID to UID/GID mappings. @@ -122,6 +152,8 @@ The major new features are: +SMB signing +security settings Full support for client and server SMB signing to ensure compatibility with default Windows 2003 security settings. @@ -145,6 +177,7 @@ complete descriptions of new or modified parameters. Removed Parameters +deleted parameters In alphabetical order, these are the parameters eliminated for Samba 3.0.20. @@ -179,6 +212,8 @@ complete descriptions of new or modified parameters. Remote Management +new parameters + abort shutdown script shutdown script @@ -397,14 +432,19 @@ complete descriptions of new or modified parameters. +Windows domain +getpwnam() call +NT_STATUS_LOGON_FAILURE When operating as a member of a Windows domain, Samba-2.2 would map any users authenticated by the remote DC to the guest account if a UID could not be obtained via the getpwnam() call. Samba-3 - rejects the connection as NT_STATUS_LOGON_FAILURE. There is no + rejects the connection as NT_STATUS_LOGON_FAILURE. There is no current workaround to re-establish the Samba-2.2 behavior. +add user script +add machine script When adding machines to a Samba-2.2 controlled domain, the add user script was used to create the UNIX identity of the machine trust account. Samba-3 introduces a new add machine @@ -426,6 +466,7 @@ complete descriptions of new or modified parameters. +encrypted passwords Encrypted passwords have been enabled by default in order to interoperate better with out-of-the-box Windows client installations. This does mean that either (a) a Samba account @@ -434,25 +475,27 @@ complete descriptions of new or modified parameters. +ADS +Kerberos +LDAP Inclusion of new ads option for integration with an Active Directory domain using the native Windows Kerberos 5 and LDAP protocols. - Samba-3 also includes the possibility of setting up chains - of authentication methods - () and account - storage backends - (). - Please refer to the &smb.conf; - man page and Chapter 10, Account Information Databases, for details. While both parameters assume sane default - values, it is likely that you will need to understand what the - values actually mean in order to ensure Samba operates correctly. +account storage backends + Samba-3 also includes the possibility of setting up chains of authentication methods () and account storage backends (). Please refer to + the &smb.conf; man page and Account Information Databases, for + details. While both parameters assume sane default values, it is likely that you will need to understand what + the values actually mean in order to ensure Samba operates correctly. pdbedit +smbpasswd +net tool Certain functions of the smbpasswd tool have been split between the new smbpasswd utility, the net tool, and the new pdbedit utility. See the respective man pages for details. @@ -471,6 +514,10 @@ complete descriptions of new or modified parameters. New Schema +object class +sambaSamAccount +LDIF +attributes A new object class (sambaSamAccount) has been introduced to replace the old sambaAccount. This change aids in the renaming of attributes to prevent clashes with attributes from other vendors. There is a @@ -480,6 +527,7 @@ complete descriptions of new or modified parameters. Example: +ldapsearch &prompt;ldapsearch .... -LLL -b "ou=people,dc=..." > old.ldif @@ -487,27 +535,34 @@ complete descriptions of new or modified parameters. +netgetlocalsid The <DOM SID> can be obtained by running &prompt;net getlocalsid <DOMAINNAME> +PDC on the Samba PDC as root. Under Samba-2.x the domain SID can be obtained by executing: +smbpasswd &prompt;smbpasswd -S <DOMAINNAME> - The old sambaAccount schema may still be used by specifying the +old sambaAccount +ldapsam_compat +object class declaration +samba.schema + The old sambaAccount schema may still be used by specifying the ldapsam_compat passdb backend. However, the sambaAccount and associated attributes have been moved to the historical section of the schema file and must be uncommented before use if needed. - The Samba-2.2 object class declaration for a sambaAccount has not changed - in the Samba-3 samba.schema file. + The Samba-2.2 object class declaration for a sambaAccount has not changed + in the Samba-3 samba.schema file. @@ -516,7 +571,13 @@ complete descriptions of new or modified parameters. - sambaDomain &smbmdash; domain information used to allocate RIDs +sambaDomain +domain information +RID +ldap suffix +ldapsam +idmap + sambaDomain &smbmdash; domain information used to allocate RIDs for users and groups as necessary. The attributes are added in ldap suffix directory entry automatically if an idmap UID/GID range has been set and the ldapsam @@ -524,6 +585,9 @@ complete descriptions of new or modified parameters. +sambaGroupMapping +ldap group suffix +net groupmap sambaGroupMapping &smbmdash; an object representing the relationship between a posixGroup and a Windows group/SID. These entries are stored in the ldap @@ -531,13 +595,19 @@ complete descriptions of new or modified parameters. - sambaUNIXIdPool &smbmdash; created in the ldap idmap suffix entry +sambaUNIXIdPool +ldap idmap suffix +idmap UID +idmap GID + sambaUNIXIdPool &smbmdash; created in the ldap idmap suffix entry automatically and contains the next available idmap UID and idmap GID. - sambaIdmapEntry &smbmdash; object storing a mapping between a +sambaIdmapEntry +idmap_ldap module + sambaIdmapEntry &smbmdash; object storing a mapping between a SID and a UNIX UID/GID. These objects are created by the idmap_ldap module as needed. @@ -549,7 +619,14 @@ complete descriptions of new or modified parameters. New Suffix for Searching - The following new smb.conf parameters have been added to aid in directing +LDAP queries +passdb backend +ldap suffix +ldap user suffix +ldap machine suffix +ldap group suffix +ldap idmap suffix + The following new &smb.conf; parameters have been added to aid in directing certain LDAP queries when passdb backend = ldapsam://... has been specified. @@ -563,9 +640,11 @@ complete descriptions of new or modified parameters. +ldap suffix +subsuffix parameters If an ldap suffix is defined, it will be appended to all of the remaining subsuffix parameters. In this case, the order of the suffix - listings in smb.conf is important. Always place the ldap suffix first + listings in &smb.conf; is important. Always place the ldap suffix first in the list. @@ -595,6 +674,7 @@ complete descriptions of new or modified parameters. +NFS This configuration allows Winbind installations on multiple servers to share a UID/GID number space, thus avoiding the interoperability problems with NFS that were present in Samba-2.2. -- cgit