1 WHATS NEW IN Samba 2.2.1: 9th July 2001
2 ========================================
4 This is the latest stable release of Samba. This is the version that all
5 production Samba servers should be running for all current bug-fixes.
7 New/Changed parameters in 2.2.1
8 -------------------------------
15 When Samba is configured to use PAM, turns on or off Samba checking
16 the PAM account restrictions. Defaults to off.
20 When Samba is configured to use PAM, turns on or off Samba passing
21 the password changes to PAM. Defaults to off.
25 New option to allow new Windows 2000 large file (64k) streaming
26 read/write options. Needs a 64 bit underlying operating system
27 (for Linux use kernel 2.4 with glibc 2.2 or above). Can improve performance
28 by 10% with Windows 2000 clients. Defaults to off. Not as tested
29 as some other Samba code paths.
33 Prevents clients from seeing the existance of files that cannot
34 be read. Off by default.
38 Turn on/off the enhanced Samba browing functionality (*1B names).
39 Default is "on". Can prevent eternal machines in workgroups when
40 WINS servers are not synchronised.
52 1). "find" command removed for smbclient. Internal code now used.
53 2). smbspool updates to retry connections from Michael Sweet.
54 3). Fix for mapping 8859-15 characters to UNICODE.
55 4). Changed "security=server" to try with invalid username to prevent
57 5). Fixes to allow Windows 2000 SP2 clients to join a Samba PDC.
58 6). Support for Windows 9x Nexus tools to allow security changes from Win9x.
59 7). Two locking fixes added. Samba 2.2.1 now passes the Clarion network
60 lock tester tool for distributed databases.
61 8). Preliminary support added for Windows 2000 large file read/write SMBs.
62 9). Changed random number generator in Samba to prevent guess attacks.
63 10). Fixes for tdb corruption in connections.tdb and file locking brlock.tdb.
64 smbd's clean the tdb files on startup and shutdown.
65 11). Fixes for default ACLs on Solaris.
66 12). Tidyup of password entry caching code.
67 13). Correct shutdowns added for send fails. Helps tdb cleanup code.
68 14). Prevent invalid '/' characters in workgroup names.
69 15). Removed more static arrays in SAMR code.
70 16). Client code is now UNICODE on the wire.
71 17). Fix 2 second timstamp resolution everywhere if dos timestamp set to yes.
72 18). All tdb opens now going through logging function.
73 19). Add pam password changing and pam restrictions code.
74 20). Printer driver management improvements (delete driver).
75 21). Fix difference between NULL security descriptors and empty
77 22). Fix SID returns for server roles.
78 23). Allow Windows 2000 mmc to view and set Samba share security descriptors.
79 24). Allow smbcontrol to forcibly disconnect a share.
80 25). tdb fixes for HPUX, OpenBSD and other OS's that don't have a coherent
81 mmap/file read/write cache.
82 26). Fix race condition in returning create disposition for file create/open.
83 27). Fix NT rewriting of security descriptors to their canonical form for
85 28). Fix for Samba running on top of Linux VFAT ftruncate bug.
86 29). Swat fixes for being run with xinetd that doesn't set the umask.
87 30). Fix for slow writes with Win9x Explorer clients. Emulates Microsoft
88 TCP stack early ack specification error.
89 31). Changed lock & persistant tdb directory to /var/cache/samba by default on
90 RedHat and Mandrake as they clear the /var/lock/samba directory on reboot.
92 Older release notes for Samba 2.2.x follow.
94 -----------------------------------------------------------------------------
95 The release notes for 2.2.0a follow :
100 This is a security bugfix release for Samba 2.2.0. This release provides the
101 following two changes *ONLY* from the 2.2.0 release.
103 1). Fix for the security hole discovered by Michal Zalewski (lcamtuf@bos.bindview.com)
104 and described in the security advisory below.
105 2). Fix for the hosts allow/hosts deny parameters not being honoured.
107 No other changes are being made for this release to ensure a security fix only.
108 For new functionality (including these security fixes) download Samba 2.2.1
109 when it is available.
111 The security advisory follows :
114 IMPORTANT: Security bugfix for Samba
115 ------------------------------------
123 A serious security hole has been discovered in all versions of Samba
124 that allows an attacker to gain root access on the target machine for
125 certain types of common Samba configuration.
127 The immediate fix is to edit your smb.conf configuration file and
128 remove all occurances of the macro "%m". Replacing occurances of %m
129 with %I is probably the best solution for most sites.
134 A remote attacker can use a netbios name containing unix path
135 characters which will then be substituted into the %m macro wherever
136 it occurs in smb.conf. This can be used to cause Samba to create a log
137 file on top of an important system file, which in turn can be used to
138 compromise security on the server.
140 The most commonly used configuration option that can be vulnerable to
141 this attack is the "log file" option. The default value for this
142 option is VARDIR/log.smbd. If the default is used then Samba is not
143 vulnerable to this attack.
145 The security hole occurs when a log file option like the following is
148 log file = /var/log/samba/%m.log
150 In that case the attacker can use a locally created symbolic link to
151 overwrite any file on the system. This requires local access to the
154 If your Samba configuration has something like the following:
156 log file = /var/log/samba/%m
158 Then the attacker could successfully compromise your server remotely
159 as no symbolic link is required. This type of configuration is very
162 The most commonly used log file configuration containing %m is the
163 distributed in the sample configuration file that comes with Samba:
165 log file = /var/log/samba/log.%m
167 in that case your machine is not vulnerable to this attack unless you
168 happen to have a subdirectory in /var/log/samba/ which starts with the
174 Thanks to Michal Zalewski (lcamtuf@bos.bindview.com) for finding this
181 While we recommend that vulnerable sites immediately change their
182 smb.conf configuration file to prevent the attack we will also be
183 making new releases of Samba within the next 24 hours to properly fix
184 the problem. Please see http://www.samba.org/ for the new releases.
186 Please report any attacks to the appropriate authority.
191 ---------------------------------------------------------------------------
193 The release notes for 2.2.0 follow :
195 This is the official Samba 2.2.0 release. This version of Samba provides
196 the following new features and enhancements.
198 Integration between Windows oplocks and NFS file opens (IRIX and Linux
199 2.4 kernel only). This gives complete data and locking integrity between
200 Windows and UNIX file access to the same data files.
202 Ability to act as an authentication source for Windows 2000 clients as
203 well as for NT4.x clients.
205 Integration with the winbind daemon that provides a single
206 sign on facility for UNIX servers in Windows 2000/NT4 networks
207 driven by a Windows 2000/NT4 PDC. winbind is not included in
208 this release, it currently must be obtained separately. We are
209 committed to including winbind in a future Samba 2.2.x release.
211 Support for native Windows 2000/NT4 printing RPCs. This includes
212 support for automatic printer driver download.
214 Support for server supported Access Control Lists (ACLs).
215 This release contains support for the following filesystems:
219 Linux Kernel with ACL patch from http://acl.bestbits.at
220 Linux Kernel with XFS ACL support.
223 FreeBSD (with external patch)
225 Other platforms will be supported as resources are
226 available to test and implement the encessary modules. If
227 you are interested in writing the support for a particular
228 ACL filesystem, please join the samba-technical mailing
229 list and coordinate your efforts.
231 On PAM (Pluggable Authentication Module) based systems - better debugging
232 messages and encrypted password users now have access control verified via
233 PAM - Note: Authentication still uses the encrypted password database.
235 Rewritten internal locking semantics for more robustness.
236 This release supports full 64 bit locking semantics on all
237 (even 32 bit) platforms. SMB locks are mapped onto POSIX
238 locks (32 bit or 64 bit) as the underlying system allows.
240 Conversion of various internal flat data structures to use
241 database records for increased performance and
244 Support for acting as a MS-DFS (Distributed File System) server.
246 Support for manipulating Samba shares using Windows client tools
247 (server manager). Per share security can be set using these tools
248 and Samba will obey the access restrictions applied.
250 Samba profiling support (see below).
252 Compile time option for enabling a (Virtual file system) VFS layer
253 to allow non-disk resources to be exported as Windows filesystems
254 (such as databases etc.).
256 The documentation in this release has been updated and converted
257 from Yodl to DocBook 4.1. There are many new parameters since 2.0.7
258 and some defaults have changed.
262 Support for collection of profile information. A shared
263 memory area has been created which contains counters for
264 the number of calls to and the amount of time spent in
265 various system calls, smb transactions and nmbd activity. See
266 the file profile.h for a complete listing of the information
267 collected. Sample code for a samba pmda (collection agent
268 for Performance Co-Pilot) has been included in the pcp
271 To enable the profile data collection code in samba, you must
272 compile samba with profile data support (run configure with
273 the --with-profiling-data option). On startup, collection of
274 data is disabled. To begin collecting data use the smbcontrol
275 program to turn on profiling (see the smbcontrol man page).
276 Profile information collection can be enabled for nmbd, all smbd
277 processes or one or more selected processes. The profiling
278 data collected is the aggragate for all processes that have
281 With samba compiled for profile data collection, you may see
282 a very slight degradation in performance even with profiling
283 collection turned off. On initial tests with NetBench on an
284 SGI Origin 200 server, this degradation was not measureable
285 with profile collection off compared to no profile collection
288 With count profile collection enabled on all clients, the
289 degradation was less than 2%. With full profile collection
290 enabled on all clients, the degradation was about 8.5%.
292 =====================================================================
294 If you think you have found a bug please email a report to :
298 As always, all bugs are our responsibility.