1 =================================
2 Release Notes for Samba 3.4.0pre1
4 =================================
7 This is the first preview release of Samba 3.4. This is *not*
8 intended for production environments and is designed for testing
9 purposes only. Please report any defects via the Samba bug reporting
10 system at https://bugzilla.samba.org/.
13 Major enhancements in Samba 3.4.0 include:
14 ------------------------------------------
17 o Samba4 and Samba3 sources are included in the tarball
19 Authentication Changes:
20 o Changed the way smbd handles untrusted domain names given during user
24 o Various fixes including printer change notificiation for Samba spoolss
28 o The remaining hand-marshalled DCE/RPC services (ntsvcs, svcctl, eventlog
29 and spoolss) were replaced by autogenerated code based on PIDL.
30 o Samba3 and Samba4 do now share a common tevent library.
31 o The code has been cleaned up and the major basic interfaces are shared with
38 On the way towards a standalone Samba AD domain controller, Samba3 and Samba4
39 branches can be built as "merged" build. That's why Samba3 and Samba4 sources
40 are included in the tarball. The merged build is possible in Samba 3.4.0, but
41 disabled by default. To learn more about the merged build,
42 please see http://wiki.samba.org/index.php/Franky.
44 According to this one, there is no "source" directory included in the tarball at
45 all. Samba3 sources are located in "source3", Samba4 sources are located in
46 "source4". The libraries have been moved to the toplevel directory.
48 To build plain Samba3, please change to "source3" and start the build as usual.
49 To build Samba4 as well, please use the "--enable-merged-build" configure
53 Authentication Changes
54 ======================
56 Previously, when Samba was a domain member and a client was connecting using an
57 untrusted domain name, such as BOGUS\user smbd would remap the untrusted
58 domain to the primary domain smbd was a member of and attempt authentication
59 using that DOMAIN\user name. This differed from how a Windows member server
60 would behave. Now, smbd will replace the BOGUS name with it's SAM name. In
61 the case where smbd is acting as a PDC this will be DOMAIN\user. In the case
62 where smbd is acting as a domain member server this will be WORKSTATION\user.
63 Thus, smbd will never assume that an incoming user name which is not qualified
64 with the same primary domain, is part of smbd's primary domain.
66 While this behavior matches Windows, it may break some workflows which depended
67 on smbd to always pass through bogus names to the DC for verification. A new
68 parameter "map untrusted to domain" can be enabled to revert to the legacy
75 The spoolss subsystem was replaced by autogenerated code based on PIDL. That fixes
76 several printing issues including printer change notificiation on Samba print
77 servers and will stabilize the printing functionality generally.
78 The support for spoolss printing with Windows Vista has been improved.
84 The remaining hand-marshalled DCE/RPC services (ntsvcs, svcctl, eventlog and
85 spoolss) were replaced by autogenerated code based on PIDL.
86 So Günther Deschner finally corrected one of the biggest mistakes in the
87 development of Samba: Hand-marshalled RPC stubs.
91 Samba3 and Samba4 do now share a common tevent library for fd and timer events.
93 The code has been cleaned up and Samba3 and Samba4 do share the major basic
94 interfaces now. That is why the libraries were moved to the toplevel directory.
95 That is one of the first steps to share code and minimize the gap between
99 ######################################################################
106 Parameter Name Description Default
107 -------------- ----------- -------
108 access based share enum New No
109 dedicated keytab file New ""
110 kerberos method New default
111 map untrusted to domain New No
112 max open files Changed Default auto detected
113 perfcount module New ""
114 use kerberos keytab Removed
123 ######################################################################
124 Reporting bugs & Development Discussion
125 #######################################
127 Please discuss this release on the samba-technical mailing list or by
128 joining the #samba-technical IRC channel on irc.freenode.net.
130 If you do report problems then please try to send high quality
131 feedback. If you don't provide vital information to help us track down
132 the problem then you will probably be ignored. All bug reports should
133 be filed under the Samba 3.4 product in the project's Bugzilla
134 database (https://bugzilla.samba.org/).
137 ======================================================================
138 == Our Code, Our Bugs, Our Responsibility.
140 ======================================================================