[OpenAFS-announce] OpenAFS 1.5.17 release available
Derrick J Brashear
Mon, 19 Mar 2007 23:13:27 -0400 (EDT)
The OpenAFS Gatekeepers announce the availability of OpenAFS
version 1.5.17. Source files and available binaries can be
accessed via the web at:
or via AFS at:
All UNIX platforms:
* Security bugfix:
- SetUID is no longer honored for the local cell by default. The
"fs setcellstatus" command must be issued for any cell the system
administrator wishes to allow setuid files in.
OpenAFS 1.5.17 is the recommended production ready release for Microsoft
Windows users supporting all Microsoft Windows operating systems from
Windows 2000 to Windows Vista including both 32-bit and 64-bit
IMPORTANT: All users are recommended to upgrade to 1.5.16 or later in
order to address a serious error that will result in data corruption. If
the network connectivity to the file server is lost while background write
operations have been queued, the writes will not succeed and that data
will not be written to the file server. This leaves a hole in the file
filled with NULs. This bug is present in all releases of OpenAFS for
Windows prior to 1.5.15 and IBM Windows AFS releases prior to 3.6 2.59.
This release of OpenAFS for Windows is built using the corrected C
Runtime Library for the Spring 2007 DST changes.
Other significant changes:
* Improved NAT behavior due to reduced probe time.
* Improved NAT behavior due to forcing a new connection before
marking a server down.
* Beta versions of the Network Identity Manager AFS plug-in must be
uninstalled prior to the installation of OpenAFS 1.5.17
* Windows Vista does not support the old WinHelp file format used by
afscreds.exe and afs_control.exe.
* On Windows Vista, afscreds.exe and afs_config.exe are not User
Account Control (UAC) compatible and must be "Run as
Administrator" in order to modify the AFS Client Configuration or
start/stop the AFS client service.
Please visit http://www.openafs.org/windows.html for up to date
information on the status of the OpenAFS for Windows client.
Bug reports should be filed to email@example.com . Reports of
success should be sent to firstname.lastname@example.org .
for the OpenAFS Gatekeepers