[OpenAFS-announce] OpenAFS 1.4.3 release candidate 1 available

Derrick J Brashear openafs-info@openafs.org
Fri, 19 Jan 2007 14:08:01 -0500 (EST)

The OpenAFS Gatekeepers announce the availability of the first 
release candidate for OpenAFS version 1.4.3.
Source files and available binaries can be accessed via the web at:


or via AFS at:

      UNIX: /afs/grand.central.org/software/openafs/candidate/1.4.3rc1/
      UNC:  \\afs\grand.central.org\software\openafs\candidate\1.4.3rc1\

Microsoft Windows:

* Integrated Logon fixed to permit automatic pts group registration by
   aklog, afscreds, etc. and to re-enable Kerberos v4 acquisition of tokens
   during logon.

* CIFS corrections:  renaming offline files, browsing directories with
   only lookup privilege, and read-only files can no longer be deleted

* maximum configurable number of stat cache entries increased to 262144

* VICECONNBAD and VICETOKENDEAD errors now handled.

* PAGs are now registered as a single large group when possible.
* Configure tests for the Linux kernel try harder to notice errors.
* The cred pool has been removed to avoid a deadlock.
* The s390x system call table can now be hooked.
* system call table hooking now uses improved range checking.

* Locking is now tracked by thread in the client.
* New interfaces in Solaris 10 are used when possible.

MacOS X:
* The AFS mount entry shows more synthetic free disk space.

All platforms:
* Server fake IP address support has been fixed.
* A server crash when AFS 3.4 jumbograms are received is fixed.
* Dead (expired) token handling in the client has been improved.
* pts chown and rename crashes have been fixed.
* asetkey builds with Heimdal.
* afsdb support in the client has been made more robust across address
* A bug in 1.4.2 vos release which can leave unused files around is fixed.
* The vldb_check tool can now do repairs.
* The fileserver's handling of expired tokens has been improved.
* A crash in butc has been fixed.

Please assist the gatekeepers by deploying this release and providing
positive or negative feedback. Bug reports should be filed to
openafs-bugs@openafs.org .  Reports of success should be sent to 
openafs-info@openafs.org .

Derrick Brashear
for the OpenAFS Gatekeepers