2 * A race condition in the rx library was fixed that resulted in
3 a deadlock in rx_NewCall when the RX_CONN_MAKECALL_WAITING flag
4 was cleared when threads were still waiting to use the
5 connection. Also, fixed a potential case in which the
6 connection could be destroyed while threads were waiting to use it.
8 * The DNLC freelist has been seen to become corrupted with still
9 active entries being stored on the freelist. Changes were made
10 to perform a better job of cleaning entries before placing them
11 onto the freelist; marking them with the correct magic value when
12 purging the list; and allowing the list to be purged on startup
13 if the cache validation fails.
15 * Windows Crash Reporting does not get triggered for afsd_service.exe
16 because it provides its own top level exception handler. This patch
17 places an explicit call to ReportCrash() on platforms which support
20 If you configure Crash Reporting via AD Policy to capture crash
21 reports within the domain, then you will receive this output.
23 * Generate MiniDumps independent of the Windows Crash Reporting.
25 (a) If an exception occurs,a minidump will be generated at the path
26 %TEMP%\afsd.dmp. The type of minidump defaults to Normal but
27 can be set to any other type via use of the
30 [HKLM\SOFTWARE\OpenAFS\Client] MiniDumpType (DWORD)
32 (b) MiniDumps can be generated at any time using the "fs minidump"
33 command. This allows you to generate a minidump without
34 stopping the process or even requiring the use of a debugger
37 * an RX connection which reports bad ticket now treats it the same way
38 the expired ticket is treated. The ticket is removed from the
39 connection and a new anonymous connection is established.
41 * fs memdump now requires that the caller be in the AFS Client Admins
44 * additional debugging information is provided in cm_Analyze when the
45 error code is ignored.
47 * Fix a regression introduced into the pioctl() client code which
48 will cause a crash in winlogon.exe, explorer.exe and fs.exe if
49 MIT KFW is not installed. (1.3.82a)
51 * Remove AFS Gateway option from OpenAFS Control Panel (1.3.82a)
54 * Fix a race condition in cm_EndCallbackGrantingCall() that
55 could leave 'nrevp' pointing to freed memory. In the process,
56 optimize the processing to ensure that the applications monitoring
57 the status of the stat cache entry are only notified at most
60 * Conditionalize access to the Explorer Shell AFS->Mount Point
61 ->Remove menu item. Disable the item if the selected item(s)
64 * Activate AFS RPC (RX) Free Packet Queues stored in Thread
65 Local Storage. This eliminates thread contention on the
66 global RX free packet queue. This should improve performance
69 * Fix the IP address filtering code to properly load/unload
70 the IPHelper DLL so that Windows XP/2003 and beyond systems
71 do not have to manually probe the registry.
73 * CleanupACLEnt() was not being called consistently with
74 the cm_scache_t object referred to by the back pointer
75 mutex locked. This could in very rare conditions lead to
76 an invalid memory access.
78 * Added a script command to the msi installer "afs_replace"
79 which can be used to replace one version of OpenAFS with
80 another without requiring an uninstall and reinstall if
81 the installed msi is no longer in its original location.
83 * Apparently the problem with multi-domain forests with cross-
84 realm trusts to non-Windows realms was not entirely solved.
85 The authentication to the AFS SMB service failed because
86 the wrong name was being used. Using ASU as an example,
87 the authentication was being performed with the name
88 "QAAD\user" (an account in the forest root) and not
89 "user@ASU.EDU (the MIT Kerberos principal used to login with)
91 The solution was to add an additional dependency on KFW
92 in order or to be able to easily obtain the client principal
93 name stored in the MSLSA ccache TGT. This information is
94 used in two locations:
96 - the pioctl() function
98 - a new WinLogon Event Handler for the "logon" event.
100 The pioctl function will now be able to use the correct
101 name when calling WNetAddConnection2() and the "logon"
102 event handler will now be able to call WNetAddConnection2().
103 The hope is that the "logon" event handler will be called
104 before the profile is loaded but I have not guarrantee
108 * Fixed a locking error in cm_TryBulkStat() which had the
109 potential of deadlocking the system for the length of time
110 it takes to perform a bulk status fetch operation.
112 * Replaced time conversion code (UnixTime <-> FILETIME) to
113 be completely arithmetic instead of relying on a bizarre
114 algorithm involving a variety of C RTL time functions.
115 This has the side effect that UnixTime and FILETIME which
116 are both stored in UTC are interpretted as UTC throughout
117 the year. Windows will apply the same localization to AFS
118 as it does to NTFS. Applications which rely on the ability
119 to sync files between the two file systems will no longer
120 see the timestamps of files in AFS change an hour relative
121 to the files stored in NTFS or Windows based backup devices.
123 * Fixed a invalid memory access under a bizarre circumstance.
124 Windows will allow a physical mass media device to be
125 installed via Plug N Play to the system and will assign it
126 the lowest available drive letter. This is true even if the
127 drive letter is currently assigned in the user session to
128 a network device via NET USE (or its equivalent.) When this
129 happens, queries sent to the CIFS server will contain invalid
130 data. This invalid data was not being caught by the AFS
131 Client Service and was resulting in a crash when Freelance
134 * Fixed a reference count error when registering callbacks
135 on a stat cache object if the callback was already registered
137 * Add a case to cm_Analyze() in order to handle the case where
138 cm_GetConnByMServers() returns CM_ERROR_NOSUCHVOLUME because
139 the server list for the volume is empty. In this case, force
140 an update of the volume info and retry.
142 * Insert a missing cm_EndCallbackGrantingCall() which could
143 result in threads waiting for a callback to complete to never
146 * In the persistent cache, there is a maximum number of volume
147 entries. Allow volume entries to be reused if the maximum
148 number have been allocated and their reference count is zero.
150 * If we already have a dead virtual connection object, don't
151 ignore the fact that additional dead vc objects must be taken
154 * Removed a deadlock condition introduced in the summer of 2004.
155 Do not hold mx locks around calls to RX functions including
156 rx_NewCall(). That is what reference counts on the rx_connection
159 * Fixed an initialization error in afslogon.dll which could
160 result in random behavior including a failure to terminate
161 the NPLogon function. (1.3.80b)
163 * Fixed an error preventing the use of SMB authentication
164 on Windows 2000. (1.3.80a)
167 * Updated CellServDB to Public CellServDB 16 Mar 2005
169 * Fixed DNS AFSDB queries to ensure that "csail" cannot be
170 misinterpretted as "csail.mit.edu" when the resolver
171 is configured to append ".mit.edu" to failed DNS queries.
173 * Fixed another case in which the client would replace connections
174 to the host when it was not necessary. In this case the
175 situation would occur if cryptall was on and the connections
176 were unauthenticated due to lack of an appropriate token.
178 * OpenAFS for Windows has failed to work at sites which are
179 utilizing a cross-realm trust between an MIT/Heimdal realm
180 and a multi-domain Windows forest when the workstation being
181 accessed is not located in the root domain. This is caused
182 by a bug in the workstation which was triggered after the
183 introduction of Windows 2003 Server. When the bug is triggered,
184 the workstation attempts to authenticate users to afsd_service.exe
185 by contacting the Domain Controller instead of using the
186 LSA loopback authentication mechanism.
188 One of the reasons this bug occurs is because the workstation
189 does not have a reliable way of knowing that the service whose
190 netbios name is "AFS" is located on the workstation. This will
191 be fixed starting in Longhorn Beta 1 by Microsoft. The
192 "BackConnectionHostNames" registry value will be used to
193 indicate that the authentications to that service name should
194 be performed using the loopback authentication mechanism.
196 In the meantime, when Logon Caching is enabled, we can force
197 afsd_service.exe to authenticate using the logon cache before
198 contacting the Domain Controller. This will work with both
199 password and smart card based logons.
201 * The allDown logic in cm_ConnByMServers() was wrong. The allDown
202 flag should not be cleared if a volume's server reference is
203 marked as "offline". In the case where all of the volume's
204 servers are either "down" or the volumes are "offline", we want
205 cm_Analyze() to process the condition as CM_ERROR_ALLOFFLINE
206 instead of as CM_ERROR_TIMEDOUT. In fact, CM_ERROR_TIMEDOUT
207 should never occur in practice.
209 In the case of CM_ERROR_ALLOFFLINE, cm_Analyze() will sleep for
210 5 seconds, clear the server down and volume busy flags, and
211 then force an update from the VLDB. This allows the client to
212 update the location of a volume if the reason for it being
213 marked offline is because it is being moved. Calls to
214 cm_ConnByMServers() will be retried either until success or
215 the RDRtimeout period is reached.
217 * Correct the Power Management code behavior in response to
218 Standby, Suspend, and Shutdown events. Instead of flushing the
219 buffers associated with the mounted SMB submounts, simply write
220 all buffers which are marked dirty.
222 * Added support for "TheseCells" to afslogon.dll. "TheseCells"
223 provides a list of cells other than the default cell for which
224 tokens should be obtained using the default Kerberos principal.
225 This functionality is logon domain specific and is only available
226 when using KFW for authentication.
228 * Fixed FindNext Invalid Handle error caused by over agressive
229 attempts at garbage collecting dirSearch entries when the
230 dirSearch ID wraps from the maximum value to 1.
232 * Add support for registry defined server preferences for VLDB and
233 File servers. See registry.txt for details.
235 * Increased default cache size to 96MB and default number of cache
238 * Fixed refCount leaks related to directory lookups and pioctl calls.
240 * Callbacks revoked during a race condition with an attempt to
241 obtain the same callback no longer result in an inaccessible
244 * New command line tool:
246 afsdacl : Set or reset the DACL to allow starting or stopping
247 the afsd service by any ordinary user.
249 Usage : afsdacl [-set | -reset] [-show]
251 -reset : Reset the DACL
252 -show : Show current DACL (SDSF)
254 * IP addresses are no longer queried once at startup. Instead IP
255 addresses are obtained as needed. Loopback adapter addresses are
256 no longer published to the server.
258 * Pay attention to the MIT KFW registry configuration for automatic
259 importation of MSLSA credentials. (SOFTWARE\MIT\Leash32,MsLsaImport)
261 * Fix (once again) case-sensitive comparisons which was apparently
264 * Activate support for vos listvol -format
266 * Population of the "AFS Client Admins" group failed on non-English
267 versions of Windows because the name of the "Administrators" group
268 is localized. Now we lookup the name of the group by using the
269 Administrators Group Alias Relative ID.
271 * Multiple cell token acquisition within afscreds.exe was broken in the
272 case of Kerberos 5 cross realm authentication. Instead of contacting
273 the KDC associated with the cell's realm, afscreds would obtain a
274 token from the KDC of the user's realm. This would result in
275 "invalid kvno errors" while authenticating to the AFS servers.
276 Unauthenticated access would work. The symptoms would vary based upon
277 whether or not the VLDB servers had been contacted using unauthenticated
278 connections prior to the user obtaining tokens.
280 * The list of ACL entries was becoming corrupted. It appears as if
281 an ACL when it expires was not being appropriately cleaned up. In
282 fact, it was left in the list of ACLs associated with the scache
285 * Changed the default @sys name list to "x86_win32 i386_w2k i386_nt40"
286 for 32-bit x86 systems. The default for itanium will be "ia64_win64"
287 and "amd64_win64" for amd 64-bit processors.
289 * When executing executables, Windows provides a mechanisms by which
290 the normal search for DLLs can be bypassed. If a file foo.exe is
291 being executed and there exists a file or directory "foo.exe.local"
292 (the contents are ignored if a file), then Windows will search for
293 DLLs first in the "foo.exe.local" directory and second in the
294 directory in which the "foo.exe" file is located.
296 Previous releases of OAFW would improperly return
297 STATUS_NOT_A_DIRECTORY instead of the expected
298 STATUS_OBJECT_PATH_NOT_FOUND. This would cause the Windows SMB client
299 to terminate the search for the DLL causing the execution of the
302 * Rework the reference counting of smb_vc_t objects. The references
303 stored in the waiting locks were not counted. This could result in
304 an assertion if the reference count drops to zero.
306 * "fs wscell" returns "Freelance.Local.Root" for the workstation cell
307 when running in freelance mode.
309 * Added support for persistent caching of file contents, stat entries,
310 volume data, cell data, and name lookup data. When the registry
311 value, "NonPersistentCaching", is not defined or set to 0 the file
312 specified by "CachePath" becomes a persistent cache file. The
313 size of the cache file is computed at run time. It has a maximum
314 size of approximately 1.2GB. The contents of the file will be
315 validated according to the rules specified by the "ValidateCache"
318 * Added support for UUIDs. UUIDs are kept for as long as the
319 cache file is intact.
321 * Added cmdebug.exe and support cache manager debugging callback
322 interfaces in afsd_service.exe.
324 Usage: cmdebug -servers <server machine> [-port <IP port>] [-long]
325 [-addrs] [-cache] [-help]
326 Where: -long print all info
327 -addrs print only host interfaces
328 -cache print only cache configuration
330 * Symlinks to \\AFS\[all\]... will now be treated the same as
331 symlinks to /afs/.... However, please use /afs/... as otherwise
332 the symlinks won't work on Unix.
334 * Correct a problem with local CellID allocation for cells whose
335 server list is obtained via DNS instead of a CellServDB file. If
336 the DNS information expires the CellID assigned to the entry will
337 be changed. This causes all of the cm_scache_t objects which refer
338 to the old cellID number to become useless. Attempts to access
339 files or directories with cm_scache_t objects using the old cellID
340 will fail since the server list cannot be obtained.
342 * Correct deadlock condition in cm_EndCallbackGrantingCall which can
343 be triggered if the volume referenced by the cm_scache_t object is
346 * The AFS Service needs to respond to SERVICE_ACCEPT_SHUTDOWN messages
347 in addition to SERVICE_ACCEPT_STOP.
349 * Move RPC shutdown until after the SMB and RX shutdown procedures
350 complete. Block until RPC shutdown is complete.
352 * Modify afslogon.dll (integrated logon) to wait for service if its
353 state is START_PENDING. If the timeout period occurs, reset to
354 the retry interval and not the sleep interval.
356 * When renewing the server list for a cell obtained via DNS AFSDB
357 records, the cm_cell_t entry must be removed from the list of all
358 cells. Otherwise, the list of cells will be corrupted.
360 * In the dcache and scache modules, use the cm_scache_t dataVersion
361 instead of the cm_fakeDirVersion.
363 * Synchronize fs.c with the unix version.
365 * The variable used to determine whether a file or virtual memory
366 mapped cache is used was not properly initialized to a default
367 value. If the registry setting "NonPersistentCaching" was not
368 set, the choice would be random. Properly initialized to be
371 * The memory mapped view was never unmapped before closing the file
372 at service shutdown. This is now properly cleaned up.
374 * Default location of Cache file is now %TEMP%\AFSCache
378 * A bug affecting new installations of 1.3.75/76 would result in
379 the creating of incorrect mountpoints in the freelance root.afs
380 volume for the default cell.
382 If "fs \\afs\all\<cellname>" lists a volume name of "root" instead
383 of "root.cell", you have been affected by the bug. To correct the
384 problem, execute the following commands:
386 fs rmmount \\afs\all\<cellname>
387 fs rmmount \\afs\all\.<cellname>
389 fs mkmount \\afs\all\<cellname> root.cell <cellname>
390 fs mkmount \\afs\all\.<cellname> root.cell <cellname> -rw
394 * A bug has been fixed in the auto-generation of Freelance root.afs
395 symlinks which produced random entries in the \\AFS\all directory.
397 * Support has been added for multi-homed servers
400 * Added a new registry value, "StoreAnsiFilenames", which can be used
401 to force the use of ANSI character sets instead of OEM Code Pages.
402 This feature is useful when users require the ability to create
403 filenames with 8-bit characters and need to access the files from
404 both Latin-1 based Unix systems as well as from Windows.
406 Activation of this feature will prevent access to files stored with
407 8-bit OEM characters.
409 * Shutdown all SMB threads in a synchronized manner when stopping the
412 * There is currently a maximum cache size of 1.3GB. The limit is imposed
413 by the largest contiguous block of unused memory within the 2GB process
414 space which can be assigned to the memory mapped file. Unfortunately,
415 when the executable digital signature verification code is activated
416 Windows sees fit to further segment the process memory which in turn
417 reduces the size of the maximum cache file to less then 800MB. If
418 larger cache sizes are desired, a new registry value should be set:
420 HKLM\SOFTWARE\OpenAFS\Client (DWORD) "VerifyServiceSignature" = 0x0
422 Setting this value will disable the runtime verification of digital
423 signatures on afsd_service.exe and the afs dlls which it loads. It
424 will not disable the the version number check on those same files.
425 The signature verification is not a security messure and is only meant
426 to enhance the ability to afsd_service.exe to detect potential
427 destablizing mixtures of DLLs from incompatible distributions.
429 Added code to auto-disable the signature verification check if
430 the desired cache size is greater then 700MB.
432 * Windows' WinTrustVerify(WIN_SPUB_ACTION_PUBLISHED_SOFTWARE) is
433 used to verify the validity of the afsd_service.exe binary
434 as well as each of the AFS DLLs loaded by the service. Not only
435 must the digital signature be valid but the signatures of the
436 DLL must be signed by the same entity as the service.
438 * Implement new functions: cm_freelanceMountPointExists and
439 cm_freelanceSymlinkExists. Use them along with other validity
440 checks in cm_freelanceAddMount and cm_freelanceAddSymlink to
441 ensure that name collisions do not occur and that empty strings
442 are not valid file names.
444 A symlink may not have a name which would resolve to a valid
445 cell name. Doing so would prevent access to the cell.
447 * Add missing cm_HoldSCacheNoLock call to Freelance mount point
448 re-initialization code. The reference counts of the fake root.afs
449 volume scache object(s) would become invalid when the mount point
450 or symlink lists were altered.
452 * Add registry entries to provide mappings from the afsdsbmt.ini
453 to the new locations for applications which count on the use
454 of the old Profile file APIs. These apps are likely to fail
455 if the user does not have administrator privileges and the
456 registry is locked down.
458 * The afs_config.exe submounts dialog had two errors.
459 First, attempts to remove entries failed because the registry
460 key was being opened without KEY_WRITE privileges.
461 Second, when editing a submount entry, changing the name
462 would add a new key and leave the original one in place.
463 Now the original submount will be removed if its name is
466 * In recent months there have been several incidents in which
467 users have experienced problems starting or accessing
468 afsd_service.exe and after significant effort has been spent
469 it has turned out that they have two versions of AFS on the
470 machine or an inconsistent set of DLLs.
472 Code has now been added to afsd_service.exe which will walk
473 the list of modules loaded by afsd_service.exe and validate
474 that the version of the AFS DLLs matches the version of the
475 afsd_service.exe executable. If they do not match the service
478 * When Freelance mode is enabled and there is no registry
479 key HKLM\SOFTWARE\OpenAFS\Client\Freelance, afsd_service.exe
480 will attempt to import the afs_freelance.ini file contents.
481 If the file does not exist, it was creating a dummy file
482 with a r/o and r/w entry for the default cell and then
483 importing those values.
485 This process has been changed. The temporary file is no
486 longer created. Also, both the OpenAFS Client install
487 directory as well as %WINDIR% are checked for previous
488 afs_freelance.ini files.
490 * Added support for VL_GetEntryByNameN(). Still need to add
491 support for VL_GetEntryByNameU() for multi-homed support.
493 * Fix a deadlock situation in afscreds.exe when canceling an
494 auto-generated Obtain Tokens dialog
497 * Fix the locking of objects during Directory Searches in the
498 SMB/CIFS server. The failure to properly lock the reference
499 counts was resulting in the premature freeing of smb_dirSearch_t
500 objects while they were still in use by the SMB/CIFS client.
501 This does not solve the "Invalid Handle" problem.
503 * Fix Find Cell By Name pioctl call to return a valid cell
504 name for the Freelance fake root.afs volume.
505 "Freelance.Local.Root".
507 * Fix the Explorer Shell Extension Symlinks->Add operation.
508 The dialog template was missing and the link destination
509 string was too short.
511 * Add support for symlinks to Freelance root.afs volume
512 Stored at HKLM\SOFTWARE\OpenAFS\Client\Freelance\Symlinks
513 <number> = "<linkname>:<relative-path>."
514 Use symlink.exe to create, list, or remove
516 * Remove the fallback to the use of KFW's KRB4 library when obtaining
517 tokens. We never obtain KRB4 tickets.
519 * Fix AFS Client Configuration Control Panel to support new SysName
522 * Fix a bug in afsd_service.exe which could result in the SysName
523 not being read from the registry.
526 * Add code to block the issuance of AFS tokens by aklog.exe or
527 afscreds.exe when the Kerberos 5 principal name contains a dot.
529 * Modify the IsAdmin() function to always treat the local SYSTEM
530 account as an AFS client administrator. Affects fs.exe and
533 * Modify the internal handling of Quota Exceeded errors
535 * Upgrade all reference count fields in the Windows cache manager
536 and the osi library to use unsigned long instead of signed short.
537 A similar fix has been applied to the afs rpc (rx) library.
539 * fix the Windows cache manager to prevent it from replacing the
540 rx_connection object associated with the cm_conn_t object on each
541 and every operation if "fs crypt" was set. This explains the
542 dramatic performance difference when crypt is used vs clear.
543 The problem: 'cryptall', a boolean flag indicating whether or not
544 "fs crypt" is set, was being compared to the rx_connection
545 cryptlevel which is either rxkad_clear:0 or rxkad_crypt:2.
546 1 != 2 and therefore the rx_connection was always destroyed
547 and replaced on each and every operation.
549 Lock the cm_conn_t object around every call to RXAFS_xxxx functions.
550 It is not safe for the cm_conn_t object to not be locked because
551 rx_DestroyConnection might be called from another thread if:
552 - the user's tokens have changed or expired
553 - the crypt mode has changed
555 This fix appears to have also taken care of the problems associated
556 with Overlapped Writes resulting in Delayed Write errors.
558 * fix NSIS installer's AdminGroup.exe to properly create and
559 remove groups when given -create or -remove. The string comparison
562 * fs sysname now accepts a list of sysname values
564 * added a new registry value HKLM\SOFTWARE\OpenAFS\Client "IoctlDebug"
565 DWORD which when set to a non-zero value will cause error message
566 text to be output to stderr from the pioctl() routine. Useful in
567 debugging failures of fs.exe, tokens.exe, etc.
569 * added a test to the power management code to only perform a
570 flush operation if there is at least one network adapter which
571 is not a loopback adapter.
573 * Fix bug in loading of registry value HKLM\SOFTWARE\OpenAFS\Client
574 "EnableKFW". This value will not be read if the key
575 HKCU\SOFTWARE\OpenAFS\Client exists; even if the "EnableKFW"
576 value under that key does not.
578 * provide mechanisms to force the use of krb524d for Kerberos 5
579 ticket to AFS token conversion. For afslogon.dll and afscreds.exe
580 there is a new registry value "Use524" and for aklog.exe a new
581 command line parameter "-m".
583 * Fix the pattern matching algorithm to properly match patterns
586 * smb_ReceiveCoreRename() was factored to produce smb_Rename()
587 which is used by both the original function and the new
588 smb_ReceiveNTRename(). smb_ReceiveNTRename() supports the
589 creation of HardLinks in addition to Renaming. smb_Link()
590 is a new function which creates HardLinks via cm_Link().
591 cm_Link() is a new vnodeops function which creates links
594 smb_ReceiveNTRename() does not support the File Copy and
595 Move Cluster Information operations described in its interface.
596 ReceiveNTRename is under documented in CIFS-TR-1p00_FINAL.pdf.
598 * When opening files via symlinks, we should follow the symlinks
599 until we reach the actual file stat cache entry. The stat cache
600 entry of the file should then be stored in the FID instead of
601 stat scache entry of the symlink.
603 * return bad operation errors for all unimplemented functions
604 even if we do not know the functions exist.
606 * Log bad packets and unknown operation packets to the trace log
608 * Map CM_ERROR_BADOP to STATUS_NOT_SUPPORTED instead of
611 * Update list of known CIFS operations to include all those listed
612 in CIFS-TR-1p00_FINAL.pdf.
614 * Modify the handling of HKLM\SOFTWARE\OpenAFS\Client\Submounts
615 to support the REG_EXPAND_SZ type.
618 * A new Windows authorization group "AFS Client Admins" is now
619 created and populated with the members of the "Administrators"
620 group. The group is used to determine which accounts on the
621 machine may be used to modify the AFS Client Configuration via
622 the UI and command line tools. afs_config.exe, fs.exe,
624 * Modify the WinLogon Logoff Event Handler to query NT4 domain
625 controllers for the remote profile path if Active Directory
626 services are not available.
628 * Fix aklog.exe to not add the AFS ID to the username
630 * PTS registration of new users to foreign cells has been added to
633 * The cm_Daemon thread is used to perform checks for
634 down servers, up servers, volumes, callback expirations,
635 lock maintenance and token expiration. Due to a gaff in
636 larger integer division the thread never performed any
637 work. Instead the current time computation would always
638 be less then the trigger times. This had an adverse affect
639 on the client's ability to maintain communication with servers,
640 keep volumes up to date, and flush user tokens and acls
641 when they have expired. This was broken when the 1.3 branch
642 was modified to support VC7 which no longer included
645 * An initialization problem with the Freelance code was
646 detected while fixing the callbackRequest. The cm_rootSCachep
647 object is obtained during afsd_InitDaemons() but the callback
648 information is incomplete. The callback information will not
649 be obtained until cm_MergeStatus is called from within
650 cm_GetCallback. Unfortunately, cm_SyncOp did not properly
651 test for the conditions under which the callback information
654 * Reports have been filed indicating that callbacks were
655 being lost. An examination of the code indicated that the
656 cm_server_t objects were not being properly reference
657 counted by the cm_scache_t and cm_callbackRequest_t objects.
658 In particular, the cm_server_t objects may have been freed
659 from beneath the cm_conn_t objects.
661 All of the reference counting is now done via the functions:
666 this improves the ability to track the referrals.
668 Each cm_BeginCallbackGranting Call now allocates a reference
669 to the cm_server_t. The cm_EndCallbackGrantingCall either
670 frees the reference or transfers it to the cm_scache_t
671 cbServerp field. These are then appropriately tracked
672 through the cm_Analyze call.
674 * Ensure that the dnlc hash table is the same size as the
675 dir name hash table (as per original author's note).
676 Increase the dnlc CM_AFSNCNAMESIZE to a multiple of 8
677 for compatibility with 64-bit systems.
679 * fix smb_ApplyV3DirListPatches to properly apply the hidden
680 attribute to dotfiles when the infoLevel < 0x101 and
681 cm_SyncOp has failed.
683 * Fix the Freelance registry initialization code. There
684 was a possibility that some systems could end up with
685 garbage in the registry during a clean install.
688 * file and directory names beginning with "." will now be given the
689 hidden attribute when the volume access is anonymous. this matches
690 the behavior when the volume access is via an authenticated user.
692 * Added a change monitor to the HKLM\SOFTWARE\OpenAFS\Client\Freelance
693 key. When a change occurs mark the root.afs data as invalid and
694 for it to be reloaded on the next access. This allows administrators
695 to modify the mount point list without restarting the service.
697 The freelance client used to provide a fake modification time for
698 the root.afs volume data and its mount points of 7/09/2001 14:24 EDT.
699 Added code to extract the last modification time of the Freelance
700 registry key and use that instead. The time now represents the
701 most recent mount point change.
703 * PTS registration of new users to foreign cells has been added to
706 * Additional Cache Control and Credential Manager options have been
707 added to the WiX installer. See deployment guide for details.
709 * The CachePath setting is now optionally a REG_EXPAND_SZ type
711 * The WiX installer has been upgraded. Version 2.0.1927.1 is now
714 * The loopback installation code may have had a problem updating the
715 %ETC%\HOSTS file which could have resulted in a premature failure.
716 Work around code has been added for the case where the file cannot
719 * The default max chunksize was increased from 15 (32K) to 17 (128K)
720 because Windows sends 64K blocks when using overlapped writes.
722 * The default number of server threads was increased from 4 to 25 to
723 better handle overlapped writes.
725 * The "AfscredsShortcutParams" registry value was not being properly
726 loaded by afscreds.exe. Therefore, the default value was always being
727 used instead of the value set by the installer.
729 * Windows XP provides downgrade attack detection to prevent an attacker
730 from being able to force the use of NTLM simply by disrupting
731 communication with the KDC. This attack cannot exist between the
732 Windows CIFS client and the AFS Client Service. Therefore, when a
733 downgrade has been detected the afs pioctl library will force the
734 establishment of a new CIFS connection using NTLM.
736 * A locking error was discovered surrounding all references to volume
737 server lists within the cm_cell.c source file.
739 * The logged into Windows username was incorrect on Terminal Server
742 * A new registry value "NonPersistentCaching" was added to the service
743 parameters key. When set to a non-zero value, the afs cache is stored
744 in the Windows paging file. There are two limitations to choosing
746 1. when persistent caching is implemented it won't work with
747 this flag set since there will be nothing to persist.
748 2. with this flag set the initial paging allocation cannot be
749 changed while the service is running
751 * An initialization bug was discovered in aklog.exe which affected users
752 who have a domain name for their afs servers which could not be mapped
756 * afs_config.exe now validates cell names against DNS in addition
757 to the CellServDB file.
759 * In order to allow the freelance client to connect to a volume with ID
760 equal to 1 on the default cell we changed the fake root.afs volume ID
761 once again. This time we choose 0xFFFFFFFF. In addition, we change
762 the cell ID of the fake root.afs volume from 1 to 0xFFFFFFFF as well.
763 It will now be impossible for a volume ID to match that of another
764 cell unless the client is connected to 0xFFFFFFFD cells. That should
765 be enough room for growth.
767 * Fix "fs mkmount" command to work with UNC paths and when
768 started from non-AFS drives. It is now possible to create a mount
769 point in the freelance fake root.afs volume with the command
771 fs mkmount \\AFS\all\<directory-name> <volume-name> <cellname>
775 fs mkmount \\AFS\all\openafs.org root.cell openafs.org
776 fs mkmount \\AFS\all\.openafs.org root.cell openafs.org -rw
778 * The algorithm used to re-attempt access to the servers associated with
779 a volume has been altered to properly address the case in which all
780 servers have been marked down. The previous algorithm did not reset
781 the server's down flags so the servers were never actually retried.
782 This caused a problem with active volumes if the network connectivity
783 was lost as could be the case with a network cable removal, wireless
784 drop, or laptop hibernation. With the fix volume access is restored
785 almost instantenously when network connectivity becomes available.
787 * Support for SMB/CIFS browsing has been added to the AFS Client Service
788 SMB server. It is now possible to use "NET VIEW \\AFS" to obtain a
789 listing of AFS submounts and freelance mount points. Support for
790 NETSHAREENUM, NETSHAREGETINFO, NETSERVERENUM2, NETSERVERGETINFO
791 significantly enhances the behavior of AFS volumes within the Explorer
792 Shell. For instance, "AFS" now shows up as server in the Explorer
793 with each submount or freelance mount point visible as a share.
794 The right click menu in each folder now works with full functionality
795 on a consistent basis.
797 * The network provider can be configured to have different behavior
798 depending on the domain that the user logs into. These settings are
799 only relevant when using integrated login. A domain refers to an
800 Active Directory (AD) domain, a trusted Kerberos (non-AD) realm or the
801 local machine (i.e. local account logins). The domain name that is
802 used for selecting the domain would be the domain that is passed into
803 the NPLogonNotify function of the network provider. (see registry.txt
806 * Added a new registry value [HKCU\SOFTWARE\OpenAFS\Client]
807 "Authentication Cell" which may be used to specify a default
808 authentication cell for afscreds.exe which is different from
809 the default cell for the AFS Client Service daemon.
811 * Added a Logoff WinLogon Event Notification function to afslogon.dll.
812 afslogon.dll moved to %WINDIR%\System32\.
813 New registry entries added to register the dll for Winlogon events.
815 The logoff event will now force a call to ktc_ForgetAllTokens()
816 using the context of the user being logged off as long as the
817 user's profile is not loaded from within AFS. If the profile
818 was loaded from AFS we can't release the tokens since the Logoff
819 event is triggered prior to the profile being written back to
820 the its source location. This is now performed in an XP SP2
823 * Windows XP SP2 Internet Connection Firewall interoperability
826 * The %WINDIR%\afsdsbmt.ini contains four sections:
827 Submounts, Drive Mappings, Active Maps and CSC Policies.
828 The Submounts and CSC policies are now stored in the registry under
829 [HKLM\SOFTWARE\OpenAFS\Client\Submounts]
830 [HKLM\SOFTWARE\OpenAFS\Client\CSCPolicy]
831 The Drive Mappings and Active Maps are stored in the registry under
832 [HKCU\SOFTWARE\OpenAFS\Client\Mappings]
833 [HKCU\SOFTWARE\OpenAFS\Client\Active Maps]
835 There is no automatic migration of this data as it would be impossible
836 to consistently migrate data to user profiles which may not be active
837 when the machine is updated.
839 * The %WINDIR%\afs_freelance.ini contains lists of mountpoints for the
840 fake root.afs volume. For the same reasons as for the cellservdb file,
841 this information should not be in %WINDIR%. This information is now
842 kept under the registry key
843 [HKLM\SOFTWARE\OpenAFS\Client\Freelance]
845 The data from the afs_freelance.ini file will be automatically
846 migrated to the registry on first execution of afsd_service.exe
848 * Keeping the CellServDB file in the location %WINDIR%\afsdcell.ini is
849 troublesome for several reasons. One, it is confusing for those who
850 expect the file to be named "CellServDB" instead of "afsdcell.ini".
851 Two, this file is not a Windows Profile formatted file. Three,
852 applications should not be reading or writing to %WINDIR%. It causes
853 problems for Windows Terminal Server.
855 The new location of CellServDB will be the OpenAFS Client install
856 directory which is by default C:\Program Files\OpenAFS\Client and can
857 be determined by querying the registry for
858 [HKLM\SOFTWARE\TransarcCorporation\AFS Client\CurrentVersion]PathName
860 The existing afsdcell.ini will be migrated by the NSIS installer.
861 The Wix installer must still be updated to do the same.
863 * Change NSIS installer to use DNS by default; to remove Integrated Logon
864 High Security mode; and to add Terminal Services compatibility registry
865 entries to allow the OpenAFS tools to find the afsdcell.ini and other
866 configuration files in %WINDIR%.
868 * Add support for authenticated SMB connections. This will remove
869 the need for high security mode in most situations. Both NTLM
870 and Extended Security (GSS SPNEGO) modes are supported. Effectively,
871 only NTLM can be used even though Kerberos is now supported. The
872 reason is that it is not possible to construct a service principal
873 which is unique to each individual machine.
875 SMB Extended Auth does not work on XP SP2 unless one of two registry
876 modifications are made:
878 (1) To disable the check for matching host names on loopback connections
879 set this key. This does not require a reboot:
881 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
882 "DisableLoopbackCheck"=dword:00000001
884 (2) To add the AFS SMB/CIFS service name to an approved list. This
885 does require a reboot:
887 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
888 "BackConnectionHostNames"=multi-sz "AFS" "MACHINE-AFS"
890 afsd_service.exe will automatically add the current Netbios Name
891 to the BackConnectionHostNames list and then temporarily disable
892 the loopback check for one cycle of startup/shutdown of the service.
893 We assume most folks do not start/stop without a reboot so this
894 will be adequate in most cases.
896 * Fix security hole in afslogon.dll which allowed passwords to be
897 sent in clear text to the KDC in a misformed principal name.
899 * Fix cm_GetCell() to properly handle expired dns entries
902 * If Freelance mode is active and the afs_freelance.ini
903 file does not exist, do not create an empty file.
904 Instead create a file containing ro and rw mountpoints
905 to the default cell using the standard conventions.
907 * Modify the Freelance support to handle the ability
908 to create rw mount points in the fake root.afs volume.
910 * Changed the RPC mechanism used for token setting from
911 named pipes to local. Use of named pipes can be restored
912 by setting the environment variable AFS_RPC_PROTSEQ to
915 Named pipes were required when a Windows 9x system was
916 using a NT system in gateway mode which is incompatible
917 with our use of local loopback adapters.
919 * In afscreds.exe, if a username of the form user@REALM is
920 specified and no password is specified, do not perform a
921 kinit operation. Only perform the aklog functionality.
923 * Add a new registry value which allows the number of processors
924 on which afsd_service.exe executes to be restricted. Valid
925 values are 1..numOfProcessors
927 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAfsDaemon\Parameters
931 * A second MSI based installer option is now available.
933 * Fixed Kerberos 5 kinit functionality in afscreds.exe to properly
934 request tickets for user/instance@REALM instead of just user@REALM
936 * Modify the Power Management Notify routine to wait for the Hard Dead
937 timeout period instead of a fixed 19 seconds. With the longer timeout
938 periods Hibernation and Standby could never succeed when network
939 connectivity is not available.
941 * The following fs.exe commands are now restricted to Administrator:
942 - checkservers with a non-zero timer value
945 - sysname with a new sysname list
954 setting the default sysname for a machine should be done via the
955 registry and not via "fs sysname".
957 * NSIS installer adds options to install Debugging Symbols
958 and the Microsoft Loopback Adapter; the user is now also
959 given the ability to select the afscreds.exe startup options.
961 * Build system modified to generate symbols for FREE (aka RELEASE)
962 builds as well as CHECKED (aka DEBUG) builds
964 * Sites which have a volume ID of 0x20000001 assigned to their
965 root.cell volumes have been experiencing problems with accessing
966 the root.cell volume of their cell when Freelance mode has been
967 active. This was because 0x20000001 was assigned to the fake
968 root.afs volume created by freelance. The fake volume id is
969 now set to 0x00000001 to prevent conflicts.
971 * The timeout logic in the AFS Client Service has been wrong
972 for sometime. It is based on two different assumptions.
973 First, the SMB client timeout is a fix value as was the case
974 with OS/2 Lan Manager. This assumption is incorrect. The
975 SMB timeout in Windows is a dynamic value computed based upon
976 a fixed minimum timeout to which is added time based upon the
977 size of the request and the performance characteristics of
978 the connection. Second, it is the responsibility of the
979 SMB Server to enforce the timeout requirements of the client.
980 This is untrue. The SMB Server cannot be expected to know
981 the requirements of the client. More importantly, if the
982 SMB server uses the SMB client timeout as a value to restrict
983 its behavior as an RX client, the performance characteristics
984 of the local SMB session would be used to prematurely terminate
985 WAN connections with significantly different performance
988 The timeout logic has therefore been modified in the following
990 . the Lan Manager Workstation (SMB) Session Timeout is used only
991 as a basis for configuring the Connection Dead Timeout
992 and Hard Dead Timeout values. The Connection Dead Timeout
993 must be at least 15 seconds longer than the SMB Timeout
994 and the Hard Dead Timeout must be at least double the
995 Connection Dead Timeout.
996 . New registry entries have been added to allow the Connection
997 Dead Timeout and Hard Dead Timeout values independent of the
998 Lan Manager Workstation Session Timeout
999 . The test to enforce the SMB Client Timeout has been removed.
1001 One of the side-effects of removing the enforcement of the SMB
1002 Client Timeout is that regardless of whether or not the SMB client
1003 is available to receive the response (and how would the SMB server
1004 know) the RX protocol response can be used to update the AFS
1005 Client Service state for ready access by future SMB client
1008 This should be the end of the "Server paused or restarting messages"
1010 * Add support for arbitrary UNC paths to the pioctl() support.
1011 This enables the fs commands as well as the AFS Shell Extension
1012 to work correctly when UNC paths are being used.
1014 * Fix afscreds.exe (by updating afskfw.lib) to search for cells via
1015 DNS if the cell configuration cannot be determined via CellServDB
1017 * Add debug info to test whether CM_BUF_WAITING or CM_SCACHE_WAITING
1018 are ever set more than once at a time
1020 * Fix the management of lists of cm_cell_t structures when using
1021 DNS to lookup cell information. The previous code would fail to
1022 reuse the same cellID for a cell if DNS was used more than once
1023 for a given cell name. When the ttl expired, a single cm_cell_t
1024 could be inserted into the cm_allCellsp list more than once
1025 producing a loop. In addition, the vlServerp list belonging to
1026 the cell was not freed resulting in improper refCounting of the
1029 * Add DNS support to cm_IoctlNewCell() which previous only examined
1032 * Add cm_FreeServer() function and call it from cm_FreeServerList()
1033 to properly garbage collect cm_server_t objects
1035 * Add numVCs variable to smb.c to track the number of smb_vc_t
1036 objects created and use it to initialize the vcID field which
1037 previously was set to 0 in all objects resulting in FindByID
1040 * Fixed DNS lookups to work consistently throughout the OpenAFS
1041 product instead of just from within the afsd_service.exe
1043 * Added a runtime check to ensure that AFS Client Service SMB
1044 Server is accepting connections before attempting to mount
1047 * Read IP addresses for volume servers out of the CellServDB
1048 file if gethostbyname() on the hostname fails.
1050 * Fix getcellconfig() to populate both the Hostnames as well
1051 as IP addresses when loading cell data via DNS
1053 * Increase the Connection Dead Time to 50 from 20 seconds
1054 Increase the Hard Dead Time to 120 from 40 seconds
1055 (matches the Unix values)
1057 * Fixed an assertion validating the number of allocated NCBs
1059 * Fixed the build environment to consistently build for
1060 Windows 2000 and above. (APPVER = 5.0)
1062 * Fixed rx_debug to properly validate the receipt in incoming
1063 data with select() and recvfrom(). Do not copy data out of
1064 the socket buffer unless success is indicated.
1067 * afsd_service.exe will now display a message box to the
1068 desktop when it terminates due to an IP Address Change.
1070 * installer no longer deletes AFS Server configuration data
1073 * installer generates a warning dialog if the RPC service
1074 is not properly configured
1076 * installer compressed with lzma instead of bzip2
1078 * afsd_service.exe shutdown crash solved once and for all
1080 * reference counting of smb_vc_t data structures improved
1082 * name space collision of smb_fid_t event objects corrected
1084 * the output of "fs memdump" is now written to
1085 %WINDIR%\TEMP\afsd_alloc.log
1087 * the file TaAfsApp_1033.dll is now properly installed allowing
1088 the User Manager to start
1090 * a new algorithm is used for computing filename pattern matches
1092 * afscreds.exe now accepts user names containing instance
1095 * Fix the Directory Name Lookup Cache to be case-sensitive.
1096 This is crucial in environments in which a Windows client
1097 is accessing a directory with more than one filename that
1098 differs only by case. If the directory contains "FOO"
1099 and "Foo". You want "DEL Foo" to delete the correct one.
1100 We still have a problem in that "DEL foo" will delete a
1101 random filename. This will be addressed in a future release.
1103 * Fix afscreds.exe -M option (renewMaps) to work when High
1104 Security mode is off. Also, remember to disable the ActiveMap
1105 flag in afsdsbmt.ini when a drive mapping is removed.
1107 * Updates to NSIS installer script. AFS Server configuration
1108 data will not be destroyed on un-install or re-install.
1109 Use a better compression algorithm.
1111 * afslogon.dll now uses KFW to obtain tokens when available
1113 * afslogon.dll when given an all uppercase username will
1114 attempt to authenticate with both the uppercase name
1115 and an all lowercase variation
1117 * DST modification removed. The fix appears to make things
1118 worse after a reboot of the machine.
1120 * fs.exe: added "cscpolicy" which is used to
1121 change client side caching policy for AFS shares
1123 Usage: fs cscpolicy [-share <AFS share>] [-manual] [-programs]
1124 [-documents] [-disable] [-help]
1126 * Several uninitialized variables have been initialized
1128 * It is now possible to obtain tokens using cross realm
1129 Kerberos within afscreds.exe:
1131 user: jaltman@ATHENA.MIT.EDU
1133 Will obtain a cross realm ticket for jaltman/DEMENTIA.ORG@ATHENA.MIT.EDU
1134 will will in turn be used to obtain afs@DEMENTIA.ORG.
1135 The resulting token will be stored with the display name
1136 jaltman@ATHENA.MIT.EDU@dementia.org
1138 * aklog.exe has been added to the client
1140 Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
1141 [[-p | -path] pathname]
1145 -d gives debugging information.
1146 krb_realm is the kerberos realm of a cell.
1147 pathname is the name of a directory to which you wish to authenticate.
1148 -noprdb means don't try to determine AFS ID.
1149 -5 or -4 selects whether to use Kerberos V or Kerberos IV.
1150 (default is Kerberos V)
1151 No commandline arguments means authenticate to the local cell.
1154 * All of the resource files have been restructured to adhere to
1155 a set of rules IBM implemented for loading string resources.
1156 These rules had either been forgotten or were not discovered
1157 by folks working on the OpenAFS sources. The end result was
1158 memory corruption. This is primary item which was preventing
1159 the AFS Server from working.
1161 * Increased the size of the maximum ticket size stored in a token
1162 from 344 bytes to 12,000. Increased the buffers used to convey
1163 messages between the pioctl() caller and the SMB Server from
1164 1000 bytes to 12,512. The code appeared to have been writing
1165 above the top of the stack by quite a few number of bytes.
1166 (The increased ticket size is necessary for the next item.)
1168 * When obtaining AFS Tokens via KFW, krb524 is no longer required.
1169 Instead the raw Kerberos 5 ticket is used in its entirety. This
1170 is extremely important as it allows us to use pure Kerberos 5 KDCs
1171 as the source of the AFS authentication. The use of up to 12,000 byte
1172 tickets will allow tickets produced by all versions of Microsoft
1173 Active Directory to be used.
1174 - create a user account.
1175 - designate it DES only
1177 - specify its UPN to be "afs@realm"
1178 - assign a SPN of "afs/cellname" to the UPN with setspn.exe
1180 * Do not enforce the funky 8dot3 pattern matching rule that the first "."
1181 is special when using long file names. (you must use "*.*" and not "*")
1182 Instead only enforce it when performing 8dot3 searches.
1184 * Fixed the DST problem with creation times being set one hour ahead
1186 * Fixed the problem when using \\afs\cell-alias. For example,
1187 \\afs\uncc instead of \\afs\uncc.edu. Do not a new cell struct
1188 for the alias name; instead simply expand the name. One of the
1189 symptoms of this problem was a loss of acquired tokens.
1191 * Fixed the AFS Shell Extension. The Symbolic Link menu was empty
1192 of strings. (Only English strings provided.)
1194 * Fixed the installer to properly replace in use files.
1196 * Fixed the build system to cleanup generated component version files
1198 * The release build compiled with MSVC 6.0 compiler to avoid the
1199 afsd_service.exe shutdown crash. This does not solve the problem
1200 but simply avoids it for the time being.
1204 * fix afslogon.dll to not corrupt memory when High Security mode
1207 * fix afsd_service.exe to not attempt to restore the stack when
1208 an exception occurs. (not safe in multi-threaded programs)
1210 * fix uninstaller to properly remove the CRT and MFC DLLs
1212 * remove a Message Box from afscreds.exe when getcellconfig()
1213 fails on a kerberos realm which is not a cell
1215 The following is a list of changes to the OpenAFS for Window client
1218 * "fs setserverprefs" will leave afsd service deadlocked
1220 * "vos listaddrs" will core dump
1222 * installer sets the appropriate keys to support Integrated Logon
1224 * installer disables the "Find Lana by Name" functionality as it
1225 was causing headaches for many users
1227 * fix the intermittent crash of the power management thread when
1228 shutting down the AFS Client Service
1230 * optimizes the obtain drive mount list functionality which is
1231 executed every time the mount tab in afscreds.exe and afs_config.exe
1232 are refreshed. (this happens a lot)
1234 * fix the service shutdown logic. add the STOP_PENDING state
1235 and do not accept additional service events after we declare
1238 The following is a list of changes to the OpenAFS for Window client
1241 * flexelint was run against the source tree and hundreds (perhaps
1242 thousands) of corrections were applied to ensure prototypes
1243 were in use; types were used consistently; variables were
1244 initialized; unused variables were removed; etc.
1246 * A wide variety of instrumentation was added including the
1247 ability to produce a stack trace from within afsd_service.exe
1250 * Dynamic configuration of the RDRtimeout value based upon the
1251 LanMan Workstation Session Timeout
1253 * The mount root no longer needs to be called "/afs". This
1254 is now set by a registry value "MountRoot" within the key
1255 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
1257 * The cell list is now only read out of afsdcell.ini when the
1258 file changes instead of each time a cell is resolved.
1260 * Thread synchronization was added to cm_server.c and ktc_nt.c
1262 * All calls to GlobalAlloc()/GlobalFree() were replaced with
1263 calloc()/free(). The Global functions were needed on Windows 3.x
1264 but have caused a variety of problems on the Win32 platforms.
1265 Avoiding them is highly recommended by several Microsoft
1266 Knowledgebase articles
1268 * Support for Symbolic Links added to the AFS Shell Extension
1270 * Added a registry value "OverlayEnabled" to determine if
1271 Shell Extension Overlays should be enabled.
1272 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
1274 * New Build system to support VC6, VC.NET, VC.NET2003 compilers and
1275 separate trees for checked and free builds. Build system supports
1276 a custom directory src\WINNT\extra which can be used as a grafting
1277 location of organization specific additions to the build tree.
1279 * New installer built using NSIS 2.0.
1281 * Named all kernel objects in order to allow them to be monitored
1282 with tools such as SysInternals' ProcExp.exe.
1284 * Introduced new EventLog framework for AFSD
1286 * Introduced Power Management interface to AFSD for Standby and
1287 Hibernate modes to allow cache to be flushed prior to network
1290 * Utilize Win32 DNSQuery API instead of internal routines. This
1291 allows DNS SRV queries to be sent to all current domain name
1292 servers. Not just one specified in an INI file. DNS is now
1295 * "NetbiosName" registry value may be used to specify a fixed
1296 Netbios Name such as "AFS" to be used instead of "HOSTNAME-AFS"
1297 when the loopback adapter is in use. If you need to use the
1298 old notation with a loopback adapter installed specify a registry
1301 "NetbiosName" REG_EXPAND_SZ = "%COMPUTERNAME%-AFS"
1303 * Refactor all modules which depend on LAN Adapter and NetbiosName
1304 determination in a new library: lanahelper.lib. This allows for
1305 consistent behavior throughout the product.
1307 * Move the afsd.log and afsd_init.log files to the directory specified
1308 by the "TEMP" environment variable. This is usually %WINDIR%\TEMP
1309 for services. Added the Date to the log entries.
1311 * New registry value "RxMaxMTU" used to limit the size of the RX
1312 packets sent by the AFS Client Service to the Server. In order
1313 to enable OpenAFS to work across the Cisco IPSec VPN the packet
1314 size must be restricted to 1264 or smaller. The latest NSIS
1315 installer sets a value of 1260 by default.
1317 * New registry value "RxNoJumbo" to disable the use of Jumbo Rx
1318 packets. This is not needed in order to work across the Cisco
1319 VPN but might be needed for other network environments. This
1320 value is not set by the NSIS installer.
1322 * New registry value "HideDotFiles" is used to apply the Hidden
1323 attribute to files whose names begin with a '.'. This value
1324 is set by the NSIS installer.
1326 * New registry value "MaxMpxRequests" allows the maximum number
1327 of multiplexed sessions to be configured at run time. This
1328 value is not set by the NSIS installer. The default value is
1331 * New registry value "MaxVCPerServer" allows the maxmimum number
1332 of VCs per server to be configured at run time. This value is
1333 not set by the NSIS installer. The default value is 100.
1335 * New registry value "AllSubmount" allows the "all" submount to
1336 be disabled by setting its value to 0x00.
1338 * Allow cells names to be valid mount points
1339 \\<netbiosName>\<cellname>
1341 * Store the active state of drive mappings in order for afscreds.exe
1342 to restore them upon startup
1344 * Add exception handling to generate a Stack Trace to the afsd_init.log
1345 file if one happens to occur.
1347 * Add lots of logging to help detect the cause of invalid SMB packets
1349 * Enable Kerberos for Windows to be used to obtain AFS Tokens via
1350 conversion of Kerberos 5 "afs" service tickets. Supports auto-
1351 renewal of expiring tokens as long as afscreds.exe is running.
1353 * New afscreds.exe command line options:
1355 -M = renew drive maps
1356 -N = ip address change detection
1359 * New registry value "EnableKFW" in {HKCU,HKLM}SOFTWARE\OpenAFS\Client
1360 determines whether or not MIT Kerberos for Windows should be used
1361 to obtain tokens via Kerberos 5 tickets.
1363 * New registry value "AfscredsShortcutParams" in
1364 {HKCU,HKLM}SOFTWARE\OpenAFS\Client
1365 determines the command line parameters to be specified when "fixing"
1366 the AFS Shortcut in the user's startup folder.
1368 * The "ShowTrayIcon" registry value has been moved from
1369 HKLM\Software\TransarcCorporation\AFS Client\AfsCreds to
1370 {HKCU,HKLM}SOFTWARE\OpenAFS\Client
1372 * The <cell name> registry values used to store the token expiration
1373 reminders have been moved from
1374 HKLM\Software\TransarcCorporation\AFS Client\AfsCreds to
1375 {HKCU,HKLM}SOFTWARE\OpenAFS\Client\Reminders
1377 * Obtain the Logon User Name from the Explorer key when available
1379 * new text document doc\txt\winnotes\registry.txt lists all registry
1380 values used by OpenAFS (excluding the AFS Server)
1382 * BUG: rx_securityClass objects were not properly reference
1383 counted and were never freed.
1385 * BUG: reduce the number of conditions under which CM_ERROR_TIMEOUT
1386 would be generated. The existence of a server does not imply
1387 that it is not down. If all of the servers for a cell are down
1388 return CM_ERROR_NOSUCHVOLUME instead. This prevents the Explorer
1391 * BUG: the directory name lookup cache failed to free the entries
1392 in the cache when the name cache entries cycled. The entries
1393 in the cache would become dereferenced without being freed.
1395 * BUG: fs setserverprefs could be executed without Administrator
1398 * BUG: the number of allocated NCB objects (100) exceeded the number
1399 which could actually be waited upon by the kernel (64). Any objects
1400 which were utilized above the limit could never have event completions
1403 * BUG: smb_username_t objects were not being reference counted and
1404 were not properly freed.
1406 * BUG: smb_tid_t objects could under unusual circumstances be freed
1407 before they were no longer referenced.
1409 * BUG: smb_fid_t object pointer were frequently used even when
1410 their value could be NULL. They were not properly released and
1411 therefore they were never freed.
1413 * BUG: smb_packet_t data structures were not completely initialized
1416 * BUG: when Rx produces a CM_ERROR_NOIPC error do not return "Access
1417 Denied" because that causes the Explorer Shell to try again until
1418 access is obtained. Instead return "Remote Resources" which allows
1419 the shell to move on and treat the error as transient.
1421 * BUG: when initializing the NCBreturns structure, separate Event objects
1422 were created for each NCB although a single Event object was supposed
1423 to be shared by all.
1425 * BUG: smb_dirSearch_t objects were not being properly referenced counted
1428 * BUG: smb_tran2Packet_t objects were not being properly referenced
1431 * BUG: directory path creation did not handle the case of multiple
1432 directories requiring creation in one attempt
1434 * BUG: SMB requests which required an Extended Response were ignored.
1435 This prevented some files from being written to AFS volumes.
1437 * BUG: character strings were being freed even after they were
1438 inserted into in use data structures
1440 * BUG: inconsistent usernames were used when High Security mode was
1441 enabled. (there is still much to do in this area)
1443 * BUG: pioctl() calls which require out of band RPC operations were
1444 susceptible to race conditions when performed by multiple processes
1446 * BUG: memory allocation and deallocation crossed instances of the
1447 C Runtime Library producing memory leakage and corruption in
1448 afscreds and the client configurator.