[OpenAFS] Re: [OpenAFS-announce] OpenAFS 1.5.30 released. Production Version for Windows.

Dave Botsch botsch@cnf.cornell.edu
Fri, 11 Jan 2008 08:28:29 -0500

When you say "no additional data will read nor written" in the CRITICAL bug
section below, do you mean that the client starts operating directly off the
network as if there is no cache, or does the client just grind completely to a


On Thu, Jan 10, 2008 at 09:29:18PM -0500, Jeffrey Altman wrote:
> 1.5.30 is the recommended production ready release of OpenAFS for
> Microsoft Windows users.  It supports all Microsoft Windows operating
> systems from Windows 2000 through Windows Vista including both 32-bit
> and 64-bit architectures.  The 1.5.30 release continues the recent
> efforts at optimizing the performance of the Windows client and
> improving its scalability.
> For UNIX, Linux, and MacOS X the recommend production ready release of
> OpenAFS is 1.4.5.  The 1.5.30 Windows client is fully compatible with
> all AFS server versions.
> Please visit http://www.openafs.org/windows.html for up to date
> information on the status of the OpenAFS for Windows client.
> For Microsoft Windows:
> This release fixes the following bugs present in 1.5.29:
>  * CRITICAL: A buffer reference count leak was introduced in 1.5.29.
>    This will cause the cache to fill and then no additional data will
>    read nor written.
>  * The Network Identity Manager AFS Provider 64-bit version would
>    crash if an AFS token configuration was set to use krb524 or
>    krb4 as the acquisition method.  KFW 64-bit includes neither
>    krb524 nor krb4 support.
>  * PTS auto-registration would fail if the Kerberos referrals
>    protocol was used to obtain the Kerberos v5 service ticket for
>    AFS.  This would occur if KFW 3.2.x is installed and there is
>    no [domain_realm] entry for the AFS volume database service
>    host domains.
>  * [Primarily on Vista] After a system resume or a network adapter
>    configuration change, communication with the AFS client service
>    could be lost.
>  * Fix "FollowBackupPath" to work with normal mount points.
>  * [Vista] A deadlock condition has been observed after resuming
>    from more than four hours of sleep.
> Other changes resulting in performance enhancements include:
>  * A new HKLM registry configuration option has been added
>    to provide hints to the Network Identity Manager AFS
>    Provider when new identities are created.  These hints
>    inform the AFS provider which cells should be configured
>    for an identity based upon the realm of the identity
>    principal.  See the release notes for details on
>    the HKLM\SOFTWARE\OpenAFS\Client\Realms\ key.
> MIT Kerberos for Windows 3.2.2
>  The recommended version of Kerberos for Windows to use with
>  OpenAFS is version 3.2.2.  KFW can be downloaded from MIT or
>  Secure Endpoints.  64-bit Windows installers for KFW are only
>  available from Secure Endpoints.
>     http://www.secure-endpoints.com/index.html#kfw
> Known issues in the Windows client:
>   . Beta versions of the Network Identity Manager AFS plug-in must
>     be uninstalled prior to the installation of OpenAFS 1.5.26
>   . Windows Vista does not support the WinHelp file format used
>     by afscreds.exe and afs_control.exe.  A download is available
>     from Microsoft.
>   . On Windows Vista, afscreds.exe is not User Account Control (UAC)
>     compatible and must be "Run as Administrator" in order to
>     start/stop the AFS client service.
> Please send reports of successful deployments to
> openafs-info@openafs.org and report problems to openafs-bugs@openafs.org.
> Jeffrey Altman
> for the OpenAFS Gatekeepers

David William Botsch
CNF Computing