+Since 1.3.82:
+ * A race condition in the rx library was fixed that resulted in
+ a deadlock in rx_NewCall when the RX_CONN_MAKECALL_WAITING flag
+ was cleared when threads were still waiting to use the
+ connection. Also, fixed a potential case in which the
+ connection could be destroyed while threads were waiting to use it.
+
+ * The DNLC freelist has been seen to become corrupted with still
+ active entries being stored on the freelist. Changes were made
+ to perform a better job of cleaning entries before placing them
+ onto the freelist; marking them with the correct magic value when
+ purging the list; and allowing the list to be purged on startup
+ if the cache validation fails.
+
+ * Windows Crash Reporting does not get triggered for afsd_service.exe
+ because it provides its own top level exception handler. This patch
+ places an explicit call to ReportCrash() on platforms which support
+ it. (XP and above.)
+
+ If you configure Crash Reporting via AD Policy to capture crash
+ reports within the domain, then you will receive this output.
+
+ * Generate MiniDumps independent of the Windows Crash Reporting.
+
+ (a) If an exception occurs,a minidump will be generated at the path
+ %TEMP%\afsd.dmp. The type of minidump defaults to Normal but
+ can be set to any other type via use of the
+ registry.
+
+ [HKLM\SOFTWARE\OpenAFS\Client] MiniDumpType (DWORD)
+
+ (b) MiniDumps can be generated at any time using the "fs minidump"
+ command. This allows you to generate a minidump without
+ stopping the process or even requiring the use of a debugger
+ on the system.
+
+ * an RX connection which reports bad ticket now treats it the same way
+ the expired ticket is treated. The ticket is removed from the
+ connection and a new anonymous connection is established.
+
+ * fs memdump now requires that the caller be in the AFS Client Admins
+ group
+
+ * additional debugging information is provided in cm_Analyze when the
+ error code is ignored.
+
+ * Fix a regression introduced into the pioctl() client code which
+ will cause a crash in winlogon.exe, explorer.exe and fs.exe if
+ MIT KFW is not installed. (1.3.82a)
+
+ * Remove AFS Gateway option from OpenAFS Control Panel (1.3.82a)
+
+Since 1.3.81:
+ * Fix a race condition in cm_EndCallbackGrantingCall() that
+ could leave 'nrevp' pointing to freed memory. In the process,
+ optimize the processing to ensure that the applications monitoring
+ the status of the stat cache entry are only notified at most
+ once.
+
+ * Conditionalize access to the Explorer Shell AFS->Mount Point
+ ->Remove menu item. Disable the item if the selected item(s)
+ are not mount points.
+
+ * Activate AFS RPC (RX) Free Packet Queues stored in Thread
+ Local Storage. This eliminates thread contention on the
+ global RX free packet queue. This should improve performance
+ on multi-CPU systems.
+
+ * Fix the IP address filtering code to properly load/unload
+ the IPHelper DLL so that Windows XP/2003 and beyond systems
+ do not have to manually probe the registry.
+
+ * CleanupACLEnt() was not being called consistently with
+ the cm_scache_t object referred to by the back pointer
+ mutex locked. This could in very rare conditions lead to
+ an invalid memory access.
+
+ * Added a script command to the msi installer "afs_replace"
+ which can be used to replace one version of OpenAFS with
+ another without requiring an uninstall and reinstall if
+ the installed msi is no longer in its original location.
+
+ * Apparently the problem with multi-domain forests with cross-
+ realm trusts to non-Windows realms was not entirely solved.
+ The authentication to the AFS SMB service failed because
+ the wrong name was being used. Using ASU as an example,
+ the authentication was being performed with the name
+ "QAAD\user" (an account in the forest root) and not
+ "user@ASU.EDU (the MIT Kerberos principal used to login with)
+
+ The solution was to add an additional dependency on KFW
+ in order or to be able to easily obtain the client principal
+ name stored in the MSLSA ccache TGT. This information is
+ used in two locations:
+
+ - the pioctl() function
+
+ - a new WinLogon Event Handler for the "logon" event.
+
+ The pioctl function will now be able to use the correct
+ name when calling WNetAddConnection2() and the "logon"
+ event handler will now be able to call WNetAddConnection2().
+ The hope is that the "logon" event handler will be called
+ before the profile is loaded but I have not guarrantee
+ that will happen.
+
Since 1.3.80:
* Fixed a locking error in cm_TryBulkStat() which had the
potential of deadlocking the system for the length of time
* Replaced time conversion code (UnixTime <-> FILETIME) to
be completely arithmetic instead of relying on a bizarre
algorithm involving a variety of C RTL time functions.
+ This has the side effect that UnixTime and FILETIME which
+ are both stored in UTC are interpretted as UTC throughout
+ the year. Windows will apply the same localization to AFS
+ as it does to NTFS. Applications which rely on the ability
+ to sync files between the two file systems will no longer
+ see the timestamps of files in AFS change an hour relative
+ to the files stored in NTFS or Windows based backup devices.
* Fixed a invalid memory access under a bizarre circumstance.
Windows will allow a physical mass media device to be