1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml">
6 <title>Samba - Release Notes Archive</title>
12 <h2>The Samba Team are pleased to announce Samba 2.2.1</h2>
16 The Samba Team is proud to announce the release of Samba 2.2.1.
18 This is the latest stable release of Samba. This is the version that all
19 production Samba servers should be running for all current bug-fixes.
21 Samba 2.2.1 is available in source form from samba.org and all of our
22 mirror sites at the url
24 <a href="/samba/ftp/samba-2.2.1a.tar.gz">/samba/ftp/samba-2.2.1a.tar.gz </a>
26 The release notes follow.
28 If you think you have found a bug please email a report to :
30 <a href="mailto:samba@samba.org">samba@samba.org</a>
32 As always, all bugs are our responsibility.
38 ----------------------------------------------------------------------
39 WHATS NEW IN Samba 2.2.1: 10th July 2001
40 =========================================
42 This is the latest stable release of Samba. This is the version that all
43 production Samba servers should be running for all current bug-fixes.
45 New/Changed parameters in 2.2.1
46 -------------------------------
53 When Samba is configured to use PAM, turns on or off Samba checking
54 the PAM account restrictions. Defaults to off.
58 When Samba is configured to use PAM, turns on or off Samba passing
59 the password changes to PAM. Defaults to off.
63 New option to allow new Windows 2000 large file (64k) streaming
64 read/write options. Needs a 64 bit underlying operating system
65 (for Linux use kernel 2.4 with glibc 2.2 or above). Can improve performance
66 by 10% with Windows 2000 clients. Defaults to off. Not as tested
67 as some other Samba code paths.
71 Prevents clients from seeing the existance of files that cannot
72 be read. Off by default.
76 Turn on/off the enhanced Samba browing functionality (*1B names).
77 Default is "on". Can prevent eternal machines in workgroups when
78 WINS servers are not synchronised.
90 1). "find" command removed for smbclient. Internal code now used.
91 2). smbspool updates to retry connections from Michael Sweet.
92 3). Fix for mapping 8859-15 characters to UNICODE.
93 4). Changed "security=server" to try with invalid username to prevent
95 5). Fixes to allow Windows 2000 SP2 clients to join a Samba PDC.
96 6). Support for Windows 9x Nexus tools to allow security changes from Win9x.
97 7). Two locking fixes added. Samba 2.2.1 now passes the Clarion network
98 lock tester tool for distributed databases.
99 8). Preliminary support added for Windows 2000 large file read/write SMBs.
100 9). Changed random number generator in Samba to prevent guess attacks.
101 10). Fixes for tdb corruption in connections.tdb and file locking brlock.tdb.
102 smbd's clean the tdb files on startup and shutdown.
103 11). Fixes for default ACLs on Solaris.
104 12). Tidyup of password entry caching code.
105 13). Correct shutdowns added for send fails. Helps tdb cleanup code.
106 14). Prevent invalid '/' characters in workgroup names.
107 15). Removed more static arrays in SAMR code.
108 16). Client code is now UNICODE on the wire.
109 17). Fix 2 second timstamp resolution everywhere if dos timestamp set to yes.
110 18). All tdb opens now going through logging function.
111 19). Add pam password changing and pam restrictions code.
112 20). Printer driver management improvements (delete driver).
113 21). Fix difference between NULL security descriptors and empty
114 security descriptors.
115 22). Fix SID returns for server roles.
116 23). Allow Windows 2000 mmc to view and set Samba share security descriptors.
117 24). Allow smbcontrol to forcibly disconnect a share.
118 25). tdb fixes for HPUX, OpenBSD and other OS's that don't have a coherent
119 mmap/file read/write cache.
120 26). Fix race condition in returning create disposition for file create/open.
121 27). Fix NT rewriting of security descriptors to their canonical form for
123 28). Fix for Samba running on top of Linux VFAT ftruncate bug.
124 29). Swat fixes for being run with xinetd that doesn't set the umask.
125 30). Fix for slow writes with Win9x Explorer clients. Emulates Microsoft
126 TCP stack early ack specification error.
127 31). Changed lock & persistant tdb directory to /var/cache/samba by default on
128 RedHat and Mandrake as they clear the /var/lock/samba directory on reboot.
130 Older release notes for Samba 2.2.x follow.
132 -----------------------------------------------------------------------------
133 The release notes for 2.2.0a follow :
138 This is a security bugfix release for Samba 2.2.0. This release provides the
139 following two changes *ONLY* from the 2.2.0 release.
141 1). Fix for the security hole discovered by Michal Zalewski (lcamtuf@bos.bindview.com)
142 and described in the security advisory below.
143 2). Fix for the hosts allow/hosts deny parameters not being honoured.
145 No other changes are being made for this release to ensure a security fix only.
146 For new functionality (including these security fixes) download Samba 2.2.1
147 when it is available.
149 The security advisory follows :
152 IMPORTANT: Security bugfix for Samba
153 ------------------------------------
161 A serious security hole has been discovered in all versions of Samba
162 that allows an attacker to gain root access on the target machine for
163 certain types of common Samba configuration.
165 The immediate fix is to edit your smb.conf configuration file and
166 remove all occurances of the macro "%m". Replacing occurances of %m
167 with %I is probably the best solution for most sites.
172 A remote attacker can use a netbios name containing unix path
173 characters which will then be substituted into the %m macro wherever
174 it occurs in smb.conf. This can be used to cause Samba to create a log
175 file on top of an important system file, which in turn can be used to
176 compromise security on the server.
178 The most commonly used configuration option that can be vulnerable to
179 this attack is the "log file" option. The default value for this
180 option is VARDIR/log.smbd. If the default is used then Samba is not
181 vulnerable to this attack.
183 The security hole occurs when a log file option like the following is
186 log file = /var/log/samba/%m.log
188 In that case the attacker can use a locally created symbolic link to
189 overwrite any file on the system. This requires local access to the
192 If your Samba configuration has something like the following:
194 log file = /var/log/samba/%m
196 Then the attacker could successfully compromise your server remotely
197 as no symbolic link is required. This type of configuration is very
200 The most commonly used log file configuration containing %m is the
201 distributed in the sample configuration file that comes with Samba:
203 log file = /var/log/samba/log.%m
205 in that case your machine is not vulnerable to this attack unless you
206 happen to have a subdirectory in /var/log/samba/ which starts with the
212 Thanks to Michal Zalewski (lcamtuf@bos.bindview.com) for finding this
219 While we recommend that vulnerable sites immediately change their
220 smb.conf configuration file to prevent the attack we will also be
221 making new releases of Samba within the next 24 hours to properly fix
222 the problem. Please see http://www.samba.org/ for the new releases.
224 Please report any attacks to the appropriate authority.
227 <a href="mailto:security@samba.org">security@samba.org</a>
229 ---------------------------------------------------------------------------
231 The release notes for 2.2.0 follow :
233 This is the official Samba 2.2.0 release. This version of Samba provides
234 the following new features and enhancements.
236 Integration between Windows oplocks and NFS file opens (IRIX and Linux
237 2.4 kernel only). This gives complete data and locking integrity between
238 Windows and UNIX file access to the same data files.
240 Ability to act as an authentication source for Windows 2000 clients as
241 well as for NT4.x clients.
243 Integration with the winbind daemon that provides a single
244 sign on facility for UNIX servers in Windows 2000/NT4 networks
245 driven by a Windows 2000/NT4 PDC. winbind is not included in
246 this release, it currently must be obtained separately. We are
247 committed to including winbind in a future Samba 2.2.x release.
249 Support for native Windows 2000/NT4 printing RPCs. This includes
250 support for automatic printer driver download.
252 Support for server supported Access Control Lists (ACLs).
253 This release contains support for the following filesystems:
257 Linux Kernel with ACL patch from http://acl.bestbits.at
258 Linux Kernel with XFS ACL support.
261 FreeBSD (with external patch)
263 Other platforms will be supported as resources are
264 available to test and implement the encessary modules. If
265 you are interested in writing the support for a particular
266 ACL filesystem, please join the samba-technical mailing
267 list and coordinate your efforts.
269 On PAM (Pluggable Authentication Module) based systems - better debugging
270 messages and encrypted password users now have access control verified via
271 PAM - Note: Authentication still uses the encrypted password database.
273 Rewritten internal locking semantics for more robustness.
274 This release supports full 64 bit locking semantics on all
275 (even 32 bit) platforms. SMB locks are mapped onto POSIX
276 locks (32 bit or 64 bit) as the underlying system allows.
278 Conversion of various internal flat data structures to use
279 database records for increased performance and
282 Support for acting as a MS-DFS (Distributed File System) server.
284 Support for manipulating Samba shares using Windows client tools
285 (server manager). Per share security can be set using these tools
286 and Samba will obey the access restrictions applied.
288 Samba profiling support (see below).
290 Compile time option for enabling a (Virtual file system) VFS layer
291 to allow non-disk resources to be exported as Windows filesystems
292 (such as databases etc.).
294 The documentation in this release has been updated and converted
295 from Yodl to DocBook 4.1. There are many new parameters since 2.0.7
296 and some defaults have changed.
300 Support for collection of profile information. A shared
301 memory area has been created which contains counters for
302 the number of calls to and the amount of time spent in
303 various system calls and smb transactions. See the file
304 profile.h for a complete listing of the information
305 collected. Sample code for a samba pmda (collection agent
306 for Performance Co-Pilot) has been included in the pcp
309 To enable the profile data collection code in samba, you
310 must compile samba with profile support (run configure with
311 the --with-profile option). On startup, collection of data
312 is disabled. To begin collecting data use the smbcontrol
313 program to turn on profiling (see the smbcontrol man page).
314 Profile information collection can be enabled for all smbd
315 processes or one or more selected processes. The profiling
316 data collected is the aggragate for all processes that have
319 With samba compiled for profile data collection, you may see
320 a very slight degradation in performance even with profiling
321 collection turned off. On initial tests with NetBench on an
322 SGI Origin 200 server, this degradation was not measureable
323 with profile collection off compared to no profile collection
326 With count profile collection enabled on all clients, the
327 degradation was less than 2%. With full profile collection
328 enabled on all clients, the degradation was about 8.5%.
330 =====================================================================
332 If you think you have found a bug please email a report to :
334 <a href="mailto:samba@samba.org">samba@samba.org</a>
336 As always, all bugs are our responsibility.