2 * The list of ACL entries was becoming corrupted because the function
3 which obtained a free entry was doing so without the appropriate lock
6 * Changed the default @sys name list to "x86_win32 i386_w2k i386_nt40"
7 for 32-bit x86 systems. The default for itanium will be "ia64_win64"
8 and "amd64_win64" for amd 64-bit processors.
10 * When executing executables, Windows provides a mechanisms by which
11 the normal search for DLLs can be bypassed. If a file foo.exe is
12 being executed and there exists a file or directory "foo.exe.local"
13 (the contents are ignored if a file), then Windows will search for
14 DLLs first in the "foo.exe.local" directory and second in the
15 directory in which the "foo.exe" file is located.
17 Previous releases of OAFW would improperly return
18 STATUS_NOT_A_DIRECTORY instead of the expected
19 STATUS_OBJECT_PATH_NOT_FOUND. This would cause the Windows SMB client
20 to terminate the search for the DLL causing the execution of the
23 * Re-work the reference counting of smb_vc_t objects. The references
24 stored in the waiting locks were not counted. This could result in
25 an assertion if the reference count drops below 0.
27 * Correct deadlock condition in cm_EndCallbackGrantingCall which can
28 be triggered if the volume referenced by the cm_scache_t object is
31 * The AFS Service needs to respond to SERVICE_ACCEPT_SHUTDOWN messages
32 in addition to SERVICE_ACCEPT_STOP.
34 * Move RPC shutdown until after the SMB and RX shutdown procedures
35 complete. Block until RPC shutdown is complete.
37 * Modify afslogon.dll (integrated logon) to wait for service if its
38 state is START_PENDING. If the timeout period occurs, reset to
39 the retry interval and not the sleep interval.
41 * When renewing the server list for a cell obtained via DNS AFSDB
42 records, the cm_cell_t entry must be removed from the list of all
43 cells. Otherwise, the list of cells will be corrupted.
45 * In the dcache and scache modules, use the cm_scache_t dataVersion
46 instead of the cm_fakeDirVersion.
48 * Synchronize fs.c with the unix version.
50 * The variable used to determine whether a file or virtual memory
51 mapped cache is used was not properly initialized to a default
52 value. If the registry setting "NonPersistentCaching" was not
53 set, the choice would be random. Properly initialized to be
56 * The memory mapped view was never unmapped before closing the file
57 at service shutdown. This is now properly cleaned up.
59 * Default location of Cache file is now %TEMP%\AFSCache
63 * A bug affecting new installations of 1.3.75/76 would result in
64 the creating of incorrect mountpoints in the freelance root.afs
65 volume for the default cell.
67 If "fs \\afs\all\<cellname>" lists a volume name of "root" instead
68 of "root.cell", you have been affected by the bug. To correct the
69 problem, execute the following commands:
71 fs rmmount \\afs\all\<cellname>
72 fs rmmount \\afs\all\.<cellname>
74 fs mkmount \\afs\all\<cellname> root.cell <cellname>
75 fs mkmount \\afs\all\.<cellname> root.cell <cellname> -rw
79 * A bug has been fixed in the auto-generation of Freelance root.afs
80 symlinks which produced random entries in the \\AFS\all directory.
82 * Support has been added for multi-homed servers
85 * Added a new registry value, "StoreAnsiFilenames", which can be used
86 to force the use of ANSI character sets instead of OEM Code Pages.
87 This feature is useful when users require the ability to create
88 filenames with 8-bit characters and need to access the files from
89 both Latin-1 based Unix systems as well as from Windows.
91 Activation of this feature will prevent access to files stored with
94 * Shutdown all SMB threads in a synchronized manner when stopping the
97 * There is currently a maximum cache size of 1.3GB. The limit is imposed
98 by the largest contiguous block of unused memory within the 2GB process
99 space which can be assigned to the memory mapped file. Unfortunately,
100 when the executable digital signature verification code is activated
101 Windows sees fit to further segment the process memory which in turn
102 reduces the size of the maximum cache file to less then 800MB. If
103 larger cache sizes are desired, a new registry value should be set:
105 HKLM\SOFTWARE\OpenAFS\Client (DWORD) "VerifyServiceSignature" = 0x0
107 Setting this value will disable the runtime verification of digital
108 signatures on afsd_service.exe and the afs dlls which it loads. It
109 will not disable the the version number check on those same files.
110 The signature verification is not a security messure and is only meant
111 to enhance the ability to afsd_service.exe to detect potential
112 destablizing mixtures of DLLs from incompatible distributions.
114 Added code to auto-disable the signature verification check if
115 the desired cache size is greater then 700MB.
117 * Windows' WinTrustVerify(WIN_SPUB_ACTION_PUBLISHED_SOFTWARE) is
118 used to verify the validity of the afsd_service.exe binary
119 as well as each of the AFS DLLs loaded by the service. Not only
120 must the digital signature be valid but the signatures of the
121 DLL must be signed by the same entity as the service.
123 * Implement new functions: cm_freelanceMountPointExists and
124 cm_freelanceSymlinkExists. Use them along with other validity
125 checks in cm_freelanceAddMount and cm_freelanceAddSymlink to
126 ensure that name collisions do not occur and that empty strings
127 are not valid file names.
129 A symlink may not have a name which would resolve to a valid
130 cell name. Doing so would prevent access to the cell.
132 * Add missing cm_HoldSCacheNoLock call to Freelance mount point
133 re-initialization code. The reference counts of the fake root.afs
134 volume scache object(s) would become invalid when the mount point
135 or symlink lists were altered.
137 * Add registry entries to provide mappings from the afsdsbmt.ini
138 to the new locations for applications which count on the use
139 of the old Profile file APIs. These apps are likely to fail
140 if the user does not have administrator privileges and the
141 registry is locked down.
143 * The afs_config.exe submounts dialog had two errors.
144 First, attempts to remove entries failed because the registry
145 key was being opened without KEY_WRITE privileges.
146 Second, when editing a submount entry, changing the name
147 would add a new key and leave the original one in place.
148 Now the original submount will be removed if its name is
151 * In recent months there have been several incidents in which
152 users have experienced problems starting or accessing
153 afsd_service.exe and after significant effort has been spent
154 it has turned out that they have two versions of AFS on the
155 machine or an inconsistent set of DLLs.
157 Code has now been added to afsd_service.exe which will walk
158 the list of modules loaded by afsd_service.exe and validate
159 that the version of the AFS DLLs matches the version of the
160 afsd_service.exe executable. If they do not match the service
163 * When Freelance mode is enabled and there is no registry
164 key HKLM\SOFTWARE\OpenAFS\Client\Freelance, afsd_service.exe
165 will attempt to import the afs_freelance.ini file contents.
166 If the file does not exist, it was creating a dummy file
167 with a r/o and r/w entry for the default cell and then
168 importing those values.
170 This process has been changed. The temporary file is no
171 longer created. Also, both the OpenAFS Client install
172 directory as well as %WINDIR% are checked for previous
173 afs_freelance.ini files.
175 * Added support for VL_GetEntryByNameN(). Still need to add
176 support for VL_GetEntryByNameU() for multi-homed support.
178 * Fix a deadlock situation in afscreds.exe when canceling an
179 auto-generated Obtain Tokens dialog
182 * Fix the locking of objects during Directory Searches in the
183 SMB/CIFS server. The failure to properly lock the reference
184 counts was resulting in the premature freeing of smb_dirSearch_t
185 objects while they were still in use by the SMB/CIFS client.
186 This does not solve the "Invalid Handle" problem.
188 * Fix Find Cell By Name pioctl call to return a valid cell
189 name for the Freelance fake root.afs volume.
190 "Freelance.Local.Root".
192 * Fix the Explorer Shell Extension Symlinks->Add operation.
193 The dialog template was missing and the link destination
194 string was too short.
196 * Add support for symlinks to Freelance root.afs volume
197 Stored at HKLM\SOFTWARE\OpenAFS\Client\Freelance\Symlinks
198 <number> = "<linkname>:<relative-path>."
199 Use symlink.exe to create, list, or remove
201 * Remove the fallback to the use of KFW's KRB4 library when obtaining
202 tokens. We never obtain KRB4 tickets.
204 * Fix AFS Client Configuration Control Panel to support new SysName
207 * Fix a bug in afsd_service.exe which could result in the SysName
208 not being read from the registry.
211 * Add code to block the issuance of AFS tokens by aklog.exe or
212 afscreds.exe when the Kerberos 5 principal name contains a dot.
214 * Modify the IsAdmin() function to always treat the local SYSTEM
215 account as an AFS client administrator. Affects fs.exe and
218 * Modify the internal handling of Quota Exceeded errors
220 * Upgrade all reference count fields in the Windows cache manager
221 and the osi library to use unsigned long instead of signed short.
222 A similar fix has been applied to the afs rpc (rx) library.
224 * fix the Windows cache manager to prevent it from replacing the
225 rx_connection object associated with the cm_conn_t object on each
226 and every operation if "fs crypt" was set. This explains the
227 dramatic performance difference when crypt is used vs clear.
228 The problem: 'cryptall', a boolean flag indicating whether or not
229 "fs crypt" is set, was being compared to the rx_connection
230 cryptlevel which is either rxkad_clear:0 or rxkad_crypt:2.
231 1 != 2 and therefore the rx_connection was always destroyed
232 and replaced on each and every operation.
234 Lock the cm_conn_t object around every call to RXAFS_xxxx functions.
235 It is not safe for the cm_conn_t object to not be locked because
236 rx_DestroyConnection might be called from another thread if:
237 - the user's tokens have changed or expired
238 - the crypt mode has changed
240 This fix appears to have also taken care of the problems associated
241 with Overlapped Writes resulting in Delayed Write errors.
243 * fix NSIS installer's AdminGroup.exe to properly create and
244 remove groups when given -create or -remove. The string comparison
247 * fs sysname now accepts a list of sysname values
249 * added a new registry value HKLM\SOFTWARE\OpenAFS\Client "IoctlDebug"
250 DWORD which when set to a non-zero value will cause error message
251 text to be output to stderr from the pioctl() routine. Useful in
252 debugging failures of fs.exe, tokens.exe, etc.
254 * added a test to the power management code to only perform a
255 flush operation if there is at least one network adapter which
256 is not a loopback adapter.
258 * Fix bug in loading of registry value HKLM\SOFTWARE\OpenAFS\Client
259 "EnableKFW". This value will not be read if the key
260 HKCU\SOFTWARE\OpenAFS\Client exists; even if the "EnableKFW"
261 value under that key does not.
263 * provide mechanisms to force the use of krb524d for Kerberos 5
264 ticket to AFS token conversion. For afslogon.dll and afscreds.exe
265 there is a new registry value "Use524" and for aklog.exe a new
266 command line parameter "-m".
268 * Fix the pattern matching algorithm to properly match patterns
271 * smb_ReceiveCoreRename() was factored to produce smb_Rename()
272 which is used by both the original function and the new
273 smb_ReceiveNTRename(). smb_ReceiveNTRename() supports the
274 creation of HardLinks in addition to Renaming. smb_Link()
275 is a new function which creates HardLinks via cm_Link().
276 cm_Link() is a new vnodeops function which creates links
279 smb_ReceiveNTRename() does not support the File Copy and
280 Move Cluster Information operations described in its interface.
281 ReceiveNTRename is under documented in CIFS-TR-1p00_FINAL.pdf.
283 * When opening files via symlinks, we should follow the symlinks
284 until we reach the actual file stat cache entry. The stat cache
285 entry of the file should then be stored in the FID instead of
286 stat scache entry of the symlink.
288 * return bad operation errors for all unimplemented functions
289 even if we do not know the functions exist.
291 * Log bad packets and unknown operation packets to the trace log
293 * Map CM_ERROR_BADOP to STATUS_NOT_SUPPORTED instead of
296 * Update list of known CIFS operations to include all those listed
297 in CIFS-TR-1p00_FINAL.pdf.
299 * Modify the handling of HKLM\SOFTWARE\OpenAFS\Client\Submounts
300 to support the REG_EXPAND_SZ type.
303 * A new Windows authorization group "AFS Client Admins" is now
304 created and populated with the members of the "Administrators"
305 group. The group is used to determine which accounts on the
306 machine may be used to modify the AFS Client Configuration via
307 the UI and command line tools. afs_config.exe, fs.exe,
309 * Modify the WinLogon Logoff Event Handler to query NT4 domain
310 controllers for the remote profile path if Active Directory
311 services are not available.
313 * Fix aklog.exe to not add the AFS ID to the username
315 * PTS registration of new users to foreign cells has been added to
318 * The cm_Daemon thread is used to perform checks for
319 down servers, up servers, volumes, callback expirations,
320 lock maintenance and token expiration. Due to a gaff in
321 larger integer division the thread never performed any
322 work. Instead the current time computation would always
323 be less then the trigger times. This had an adverse affect
324 on the client's ability to maintain communication with servers,
325 keep volumes up to date, and flush user tokens and acls
326 when they have expired. This was broken when the 1.3 branch
327 was modified to support VC7 which no longer included
330 * An initialization problem with the Freelance code was
331 detected while fixing the callbackRequest. The cm_rootSCachep
332 object is obtained during afsd_InitDaemons() but the callback
333 information is incomplete. The callback information will not
334 be obtained until cm_MergeStatus is called from within
335 cm_GetCallback. Unfortunately, cm_SyncOp did not properly
336 test for the conditions under which the callback information
339 * Reports have been filed indicating that callbacks were
340 being lost. An examination of the code indicated that the
341 cm_server_t objects were not being properly reference
342 counted by the cm_scache_t and cm_callbackRequest_t objects.
343 In particular, the cm_server_t objects may have been freed
344 from beneath the cm_conn_t objects.
346 All of the reference counting is now done via the functions:
351 this improves the ability to track the referrals.
353 Each cm_BeginCallbackGranting Call now allocates a reference
354 to the cm_server_t. The cm_EndCallbackGrantingCall either
355 frees the reference or transfers it to the cm_scache_t
356 cbServerp field. These are then appropriately tracked
357 through the cm_Analyze call.
359 * Ensure that the dnlc hash table is the same size as the
360 dir name hash table (as per original author's note).
361 Increase the dnlc CM_AFSNCNAMESIZE to a multiple of 8
362 for compatibility with 64-bit systems.
364 * fix smb_ApplyV3DirListPatches to properly apply the hidden
365 attribute to dotfiles when the infoLevel < 0x101 and
366 cm_SyncOp has failed.
368 * Fix the Freelance registry initialization code. There
369 was a possibility that some systems could end up with
370 garbage in the registry during a clean install.
373 * file and directory names beginning with "." will now be given the
374 hidden attribute when the volume access is anonymous. this matches
375 the behavior when the volume access is via an authenticated user.
377 * Added a change monitor to the HKLM\SOFTWARE\OpenAFS\Client\Freelance
378 key. When a change occurs mark the root.afs data as invalid and
379 for it to be reloaded on the next access. This allows administrators
380 to modify the mount point list without restarting the service.
382 The freelance client used to provide a fake modification time for
383 the root.afs volume data and its mount points of 7/09/2001 14:24 EDT.
384 Added code to extract the last modification time of the Freelance
385 registry key and use that instead. The time now represents the
386 most recent mount point change.
388 * PTS registration of new users to foreign cells has been added to
391 * Additional Cache Control and Credential Manager options have been
392 added to the WiX installer. See deployment guide for details.
394 * The CachePath setting is now optionally a REG_EXPAND_SZ type
396 * The WiX installer has been upgraded. Version 2.0.1927.1 is now
399 * The loopback installation code may have had a problem updating the
400 %ETC%\HOSTS file which could have resulted in a premature failure.
401 Work around code has been added for the case where the file cannot
404 * The default max chunksize was increased from 15 (32K) to 17 (128K)
405 because Windows sends 64K blocks when using overlapped writes.
407 * The default number of server threads was increased from 4 to 25 to
408 better handle overlapped writes.
410 * The "AfscredsShortcutParams" registry value was not being properly
411 loaded by afscreds.exe. Therefore, the default value was always being
412 used instead of the value set by the installer.
414 * Windows XP provides downgrade attack detection to prevent an attacker
415 from being able to force the use of NTLM simply by disrupting
416 communication with the KDC. This attack cannot exist between the
417 Windows CIFS client and the AFS Client Service. Therefore, when a
418 downgrade has been detected the afs pioctl library will force the
419 establishment of a new CIFS connection using NTLM.
421 * A locking error was discovered surrounding all references to volume
422 server lists within the cm_cell.c source file.
424 * The logged into Windows username was incorrect on Terminal Server
427 * A new registry value "NonPersistentCaching" was added to the service
428 parameters key. When set to a non-zero value, the afs cache is stored
429 in the Windows paging file. There are two limitations to choosing
431 1. when persistent caching is implemented it won't work with
432 this flag set since there will be nothing to persist.
433 2. with this flag set the initial paging allocation cannot be
434 changed while the service is running
436 * An initialization bug was discovered in aklog.exe which affected users
437 who have a domain name for their afs servers which could not be mapped
441 * afs_config.exe now validates cell names against DNS in addition
442 to the CellServDB file.
444 * In order to allow the freelance client to connect to a volume with ID
445 equal to 1 on the default cell we changed the fake root.afs volume ID
446 once again. This time we choose 0xFFFFFFFF. In addition, we change
447 the cell ID of the fake root.afs volume from 1 to 0xFFFFFFFF as well.
448 It will now be impossible for a volume ID to match that of another
449 cell unless the client is connected to 0xFFFFFFFD cells. That should
450 be enough room for growth.
452 * Fix "fs mkmount" command to work with UNC paths and when
453 started from non-AFS drives. It is now possible to create a mount
454 point in the freelance fake root.afs volume with the command
456 fs mkmount \\AFS\all\<directory-name> <volume-name> <cellname>
460 fs mkmount \\AFS\all\openafs.org root.cell openafs.org
461 fs mkmount \\AFS\all\.openafs.org root.cell openafs.org -rw
463 * The algorithm used to re-attempt access to the servers associated with
464 a volume has been altered to properly address the case in which all
465 servers have been marked down. The previous algorithm did not reset
466 the server's down flags so the servers were never actually retried.
467 This caused a problem with active volumes if the network connectivity
468 was lost as could be the case with a network cable removal, wireless
469 drop, or laptop hibernation. With the fix volume access is restored
470 almost instantenously when network connectivity becomes available.
472 * Support for SMB/CIFS browsing has been added to the AFS Client Service
473 SMB server. It is now possible to use "NET VIEW \\AFS" to obtain a
474 listing of AFS submounts and freelance mount points. Support for
475 NETSHAREENUM, NETSHAREGETINFO, NETSERVERENUM2, NETSERVERGETINFO
476 significantly enhances the behavior of AFS volumes within the Explorer
477 Shell. For instance, "AFS" now shows up as server in the Explorer
478 with each submount or freelance mount point visible as a share.
479 The right click menu in each folder now works with full functionality
480 on a consistent basis.
482 * The network provider can be configured to have different behavior
483 depending on the domain that the user logs into. These settings are
484 only relevant when using integrated login. A domain refers to an
485 Active Directory (AD) domain, a trusted Kerberos (non-AD) realm or the
486 local machine (i.e. local account logins). The domain name that is
487 used for selecting the domain would be the domain that is passed into
488 the NPLogonNotify function of the network provider. (see registry.txt
491 * Added a new registry value [HKCU\SOFTWARE\OpenAFS\Client]
492 "Authentication Cell" which may be used to specify a default
493 authentication cell for afscreds.exe which is different from
494 the default cell for the AFS Client Service daemon.
496 * Added a Logoff WinLogon Event Notification function to afslogon.dll.
497 afslogon.dll moved to %WINDIR%\System32\.
498 New registry entries added to register the dll for Winlogon events.
500 The logoff event will now force a call to ktc_ForgetAllTokens()
501 using the context of the user being logged off as long as the
502 user's profile is not loaded from within AFS. If the profile
503 was loaded from AFS we can't release the tokens since the Logoff
504 event is triggered prior to the profile being written back to
505 the its source location. This is now performed in an XP SP2
508 * Windows XP SP2 Internet Connection Firewall interoperability
511 * The %WINDIR%\afsdsbmt.ini contains four sections:
512 Submounts, Drive Mappings, Active Maps and CSC Policies.
513 The Submounts and CSC policies are now stored in the registry under
514 [HKLM\SOFTWARE\OpenAFS\Client\Submounts]
515 [HKLM\SOFTWARE\OpenAFS\Client\CSCPolicy]
516 The Drive Mappings and Active Maps are stored in the registry under
517 [HKCU\SOFTWARE\OpenAFS\Client\Mappings]
518 [HKCU\SOFTWARE\OpenAFS\Client\Active Maps]
520 There is no automatic migration of this data as it would be impossible
521 to consistently migrate data to user profiles which may not be active
522 when the machine is updated.
524 * The %WINDIR%\afs_freelance.ini contains lists of mountpoints for the
525 fake root.afs volume. For the same reasons as for the cellservdb file,
526 this information should not be in %WINDIR%. This information is now
527 kept under the registry key
528 [HKLM\SOFTWARE\OpenAFS\Client\Freelance]
530 The data from the afs_freelance.ini file will be automatically
531 migrated to the registry on first execution of afsd_service.exe
533 * Keeping the CellServDB file in the location %WINDIR%\afsdcell.ini is
534 troublesome for several reasons. One, it is confusing for those who
535 expect the file to be named "CellServDB" instead of "afsdcell.ini".
536 Two, this file is not a Windows Profile formatted file. Three,
537 applications should not be reading or writing to %WINDIR%. It causes
538 problems for Windows Terminal Server.
540 The new location of CellServDB will be the OpenAFS Client install
541 directory which is by default C:\Program Files\OpenAFS\Client and can
542 be determined by querying the registry for
543 [HKLM\SOFTWARE\TransarcCorporation\AFS Client\CurrentVersion]PathName
545 The existing afsdcell.ini will be migrated by the NSIS installer.
546 The Wix installer must still be updated to do the same.
548 * Change NSIS installer to use DNS by default; to remove Integrated Logon
549 High Security mode; and to add Terminal Services compatibility registry
550 entries to allow the OpenAFS tools to find the afsdcell.ini and other
551 configuration files in %WINDIR%.
553 * Add support for authenticated SMB connections. This will remove
554 the need for high security mode in most situations. Both NTLM
555 and Extended Security (GSS SPNEGO) modes are supported. Effectively,
556 only NTLM can be used even though Kerberos is now supported. The
557 reason is that it is not possible to construct a service principal
558 which is unique to each individual machine.
560 SMB Extended Auth does not work on XP SP2 unless one of two registry
561 modifications are made:
563 (1) To disable the check for matching host names on loopback connections
564 set this key. This does not require a reboot:
566 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
567 "DisableLoopbackCheck"=dword:00000001
569 (2) To add the AFS SMB/CIFS service name to an approved list. This
570 does require a reboot:
572 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
573 "BackConnectionHostNames"=multi-sz "AFS" "MACHINE-AFS"
575 afsd_service.exe will automatically add the current Netbios Name
576 to the BackConnectionHostNames list and then temporarily disable
577 the loopback check for one cycle of startup/shutdown of the service.
578 We assume most folks do not start/stop without a reboot so this
579 will be adequate in most cases.
581 * Fix security hole in afslogon.dll which allowed passwords to be
582 sent in clear text to the KDC in a misformed principal name.
584 * Fix cm_GetCell() to properly handle expired dns entries
587 * If Freelance mode is active and the afs_freelance.ini
588 file does not exist, do not create an empty file.
589 Instead create a file containing ro and rw mountpoints
590 to the default cell using the standard conventions.
592 * Modify the Freelance support to handle the ability
593 to create rw mount points in the fake root.afs volume.
595 * Changed the RPC mechanism used for token setting from
596 named pipes to local. Use of named pipes can be restored
597 by setting the environment variable AFS_RPC_PROTSEQ to
600 Named pipes were required when a Windows 9x system was
601 using a NT system in gateway mode which is incompatible
602 with our use of local loopback adapters.
604 * In afscreds.exe, if a username of the form user@REALM is
605 specified and no password is specified, do not perform a
606 kinit operation. Only perform the aklog functionality.
608 * Add a new registry value which allows the number of processors
609 on which afsd_service.exe executes to be restricted. Valid
610 values are 1..numOfProcessors
612 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAfsDaemon\Parameters
616 * A second MSI based installer option is now available.
618 * Fixed Kerberos 5 kinit functionality in afscreds.exe to properly
619 request tickets for user/instance@REALM instead of just user@REALM
621 * Modify the Power Management Notify routine to wait for the Hard Dead
622 timeout period instead of a fixed 19 seconds. With the longer timeout
623 periods Hibernation and Standby could never succeed when network
624 connectivity is not available.
626 * The following fs.exe commands are now restricted to Administrator:
627 - checkservers with a non-zero timer value
630 - sysname with a new sysname list
639 setting the default sysname for a machine should be done via the
640 registry and not via "fs sysname".
642 * NSIS installer adds options to install Debugging Symbols
643 and the Microsoft Loopback Adapter; the user is now also
644 given the ability to select the afscreds.exe startup options.
646 * Build system modified to generate symbols for FREE (aka RELEASE)
647 builds as well as CHECKED (aka DEBUG) builds
649 * Sites which have a volume ID of 0x20000001 assigned to their
650 root.cell volumes have been experiencing problems with accessing
651 the root.cell volume of their cell when Freelance mode has been
652 active. This was because 0x20000001 was assigned to the fake
653 root.afs volume created by freelance. The fake volume id is
654 now set to 0x00000001 to prevent conflicts.
656 * The timeout logic in the AFS Client Service has been wrong
657 for sometime. It is based on two different assumptions.
658 First, the SMB client timeout is a fix value as was the case
659 with OS/2 Lan Manager. This assumption is incorrect. The
660 SMB timeout in Windows is a dynamic value computed based upon
661 a fixed minimum timeout to which is added time based upon the
662 size of the request and the performance characteristics of
663 the connection. Second, it is the responsibility of the
664 SMB Server to enforce the timeout requirements of the client.
665 This is untrue. The SMB Server cannot be expected to know
666 the requirements of the client. More importantly, if the
667 SMB server uses the SMB client timeout as a value to restrict
668 its behavior as an RX client, the performance characteristics
669 of the local SMB session would be used to prematurely terminate
670 WAN connections with significantly different performance
673 The timeout logic has therefore been modified in the following
675 . the Lan Manager Workstation (SMB) Session Timeout is used only
676 as a basis for configuring the Connection Dead Timeout
677 and Hard Dead Timeout values. The Connection Dead Timeout
678 must be at least 15 seconds longer than the SMB Timeout
679 and the Hard Dead Timeout must be at least double the
680 Connection Dead Timeout.
681 . New registry entries have been added to allow the Connection
682 Dead Timeout and Hard Dead Timeout values independent of the
683 Lan Manager Workstation Session Timeout
684 . The test to enforce the SMB Client Timeout has been removed.
686 One of the side-effects of removing the enforcement of the SMB
687 Client Timeout is that regardless of whether or not the SMB client
688 is available to receive the response (and how would the SMB server
689 know) the RX protocol response can be used to update the AFS
690 Client Service state for ready access by future SMB client
693 This should be the end of the "Server paused or restarting messages"
695 * Add support for arbitrary UNC paths to the pioctl() support.
696 This enables the fs commands as well as the AFS Shell Extension
697 to work correctly when UNC paths are being used.
699 * Fix afscreds.exe (by updating afskfw.lib) to search for cells via
700 DNS if the cell configuration cannot be determined via CellServDB
702 * Add debug info to test whether CM_BUF_WAITING or CM_SCACHE_WAITING
703 are ever set more than once at a time
705 * Fix the management of lists of cm_cell_t structures when using
706 DNS to lookup cell information. The previous code would fail to
707 reuse the same cellID for a cell if DNS was used more than once
708 for a given cell name. When the ttl expired, a single cm_cell_t
709 could be inserted into the cm_allCellsp list more than once
710 producing a loop. In addition, the vlServerp list belonging to
711 the cell was not freed resulting in improper refCounting of the
714 * Add DNS support to cm_IoctlNewCell() which previous only examined
717 * Add cm_FreeServer() function and call it from cm_FreeServerList()
718 to properly garbage collect cm_server_t objects
720 * Add numVCs variable to smb.c to track the number of smb_vc_t
721 objects created and use it to initialize the vcID field which
722 previously was set to 0 in all objects resulting in FindByID
725 * Fixed DNS lookups to work consistently throughout the OpenAFS
726 product instead of just from within the afsd_service.exe
728 * Added a runtime check to ensure that AFS Client Service SMB
729 Server is accepting connections before attempting to mount
732 * Read IP addresses for volume servers out of the CellServDB
733 file if gethostbyname() on the hostname fails.
735 * Fix getcellconfig() to populate both the Hostnames as well
736 as IP addresses when loading cell data via DNS
738 * Increase the Connection Dead Time to 50 from 20 seconds
739 Increase the Hard Dead Time to 120 from 40 seconds
740 (matches the Unix values)
742 * Fixed an assertion validating the number of allocated NCBs
744 * Fixed the build environment to consistently build for
745 Windows 2000 and above. (APPVER = 5.0)
747 * Fixed rx_debug to properly validate the receipt in incoming
748 data with select() and recvfrom(). Do not copy data out of
749 the socket buffer unless success is indicated.
752 * afsd_service.exe will now display a message box to the
753 desktop when it terminates due to an IP Address Change.
755 * installer no longer deletes AFS Server configuration data
758 * installer generates a warning dialog if the RPC service
759 is not properly configured
761 * installer compressed with lzma instead of bzip2
763 * afsd_service.exe shutdown crash solved once and for all
765 * reference counting of smb_vc_t data structures improved
767 * name space collision of smb_fid_t event objects corrected
769 * the output of "fs memdump" is now written to
770 %WINDIR%\TEMP\afsd_alloc.log
772 * the file TaAfsApp_1033.dll is now properly installed allowing
773 the User Manager to start
775 * a new algorithm is used for computing filename pattern matches
777 * afscreds.exe now accepts user names containing instance
780 * Fix the Directory Name Lookup Cache to be case-sensitive.
781 This is crucial in environments in which a Windows client
782 is accessing a directory with more than one filename that
783 differs only by case. If the directory contains "FOO"
784 and "Foo". You want "DEL Foo" to delete the correct one.
785 We still have a problem in that "DEL foo" will delete a
786 random filename. This will be addressed in a future release.
788 * Fix afscreds.exe -M option (renewMaps) to work when High
789 Security mode is off. Also, remember to disable the ActiveMap
790 flag in afsdsbmt.ini when a drive mapping is removed.
792 * Updates to NSIS installer script. AFS Server configuration
793 data will not be destroyed on un-install or re-install.
794 Use a better compression algorithm.
796 * afslogon.dll now uses KFW to obtain tokens when available
798 * afslogon.dll when given an all uppercase username will
799 attempt to authenticate with both the uppercase name
800 and an all lowercase variation
802 * DST modification removed. The fix appears to make things
803 worse after a reboot of the machine.
805 * fs.exe: added "cscpolicy" which is used to
806 change client side caching policy for AFS shares
808 Usage: fs cscpolicy [-share <AFS share>] [-manual] [-programs]
809 [-documents] [-disable] [-help]
811 * Several uninitialized variables have been initialized
813 * It is now possible to obtain tokens using cross realm
814 Kerberos within afscreds.exe:
816 user: jaltman@ATHENA.MIT.EDU
818 Will obtain a cross realm ticket for jaltman/DEMENTIA.ORG@ATHENA.MIT.EDU
819 will will in turn be used to obtain afs@DEMENTIA.ORG.
820 The resulting token will be stored with the display name
821 jaltman@ATHENA.MIT.EDU@dementia.org
823 * aklog.exe has been added to the client
825 Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
826 [[-p | -path] pathname]
830 -d gives debugging information.
831 krb_realm is the kerberos realm of a cell.
832 pathname is the name of a directory to which you wish to authenticate.
833 -noprdb means don't try to determine AFS ID.
834 -5 or -4 selects whether to use Kerberos V or Kerberos IV.
835 (default is Kerberos V)
836 No commandline arguments means authenticate to the local cell.
839 * All of the resource files have been restructured to adhere to
840 a set of rules IBM implemented for loading string resources.
841 These rules had either been forgotten or were not discovered
842 by folks working on the OpenAFS sources. The end result was
843 memory corruption. This is primary item which was preventing
844 the AFS Server from working.
846 * Increased the size of the maximum ticket size stored in a token
847 from 344 bytes to 12,000. Increased the buffers used to convey
848 messages between the pioctl() caller and the SMB Server from
849 1000 bytes to 12,512. The code appeared to have been writing
850 above the top of the stack by quite a few number of bytes.
851 (The increased ticket size is necessary for the next item.)
853 * When obtaining AFS Tokens via KFW, krb524 is no longer required.
854 Instead the raw Kerberos 5 ticket is used in its entirety. This
855 is extremely important as it allows us to use pure Kerberos 5 KDCs
856 as the source of the AFS authentication. The use of up to 12,000 byte
857 tickets will allow tickets produced by all versions of Microsoft
858 Active Directory to be used.
859 - create a user account.
860 - designate it DES only
862 - specify its UPN to be "afs@realm"
863 - assign a SPN of "afs/cellname" to the UPN with setspn.exe
865 * Do not enforce the funky 8dot3 pattern matching rule that the first "."
866 is special when using long file names. (you must use "*.*" and not "*")
867 Instead only enforce it when performing 8dot3 searches.
869 * Fixed the DST problem with creation times being set one hour ahead
871 * Fixed the problem when using \\afs\cell-alias. For example,
872 \\afs\uncc instead of \\afs\uncc.edu. Do not a new cell struct
873 for the alias name; instead simply expand the name. One of the
874 symptoms of this problem was a loss of acquired tokens.
876 * Fixed the AFS Shell Extension. The Symbolic Link menu was empty
877 of strings. (Only English strings provided.)
879 * Fixed the installer to properly replace in use files.
881 * Fixed the build system to cleanup generated component version files
883 * The release build compiled with MSVC 6.0 compiler to avoid the
884 afsd_service.exe shutdown crash. This does not solve the problem
885 but simply avoids it for the time being.
889 * fix afslogon.dll to not corrupt memory when High Security mode
892 * fix afsd_service.exe to not attempt to restore the stack when
893 an exception occurs. (not safe in multi-threaded programs)
895 * fix uninstaller to properly remove the CRT and MFC DLLs
897 * remove a Message Box from afscreds.exe when getcellconfig()
898 fails on a kerberos realm which is not a cell
900 The following is a list of changes to the OpenAFS for Window client
903 * "fs setserverprefs" will leave afsd service deadlocked
905 * "vos listaddrs" will core dump
907 * installer sets the appropriate keys to support Integrated Logon
909 * installer disables the "Find Lana by Name" functionality as it
910 was causing headaches for many users
912 * fix the intermittent crash of the power management thread when
913 shutting down the AFS Client Service
915 * optimizes the obtain drive mount list functionality which is
916 executed every time the mount tab in afscreds.exe and afs_config.exe
917 are refreshed. (this happens a lot)
919 * fix the service shutdown logic. add the STOP_PENDING state
920 and do not accept additional service events after we declare
923 The following is a list of changes to the OpenAFS for Window client
926 * flexelint was run against the source tree and hundreds (perhaps
927 thousands) of corrections were applied to ensure prototypes
928 were in use; types were used consistently; variables were
929 initialized; unused variables were removed; etc.
931 * A wide variety of instrumentation was added including the
932 ability to produce a stack trace from within afsd_service.exe
935 * Dynamic configuration of the RDRtimeout value based upon the
936 LanMan Workstation Session Timeout
938 * The mount root no longer needs to be called "/afs". This
939 is now set by a registry value "MountRoot" within the key
940 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
942 * The cell list is now only read out of afsdcell.ini when the
943 file changes instead of each time a cell is resolved.
945 * Thread synchronization was added to cm_server.c and ktc_nt.c
947 * All calls to GlobalAlloc()/GlobalFree() were replaced with
948 calloc()/free(). The Global functions were needed on Windows 3.x
949 but have caused a variety of problems on the Win32 platforms.
950 Avoiding them is highly recommended by several Microsoft
951 Knowledgebase articles
953 * Support for Symbolic Links added to the AFS Shell Extension
955 * Added a registry value "OverlayEnabled" to determine if
956 Shell Extension Overlays should be enabled.
957 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
959 * New Build system to support VC6, VC.NET, VC.NET2003 compilers and
960 separate trees for checked and free builds. Build system supports
961 a custom directory src\WINNT\extra which can be used as a grafting
962 location of organization specific additions to the build tree.
964 * New installer built using NSIS 2.0.
966 * Named all kernel objects in order to allow them to be monitored
967 with tools such as SysInternals' ProcExp.exe.
969 * Introduced new EventLog framework for AFSD
971 * Introduced Power Management interface to AFSD for Standby and
972 Hibernate modes to allow cache to be flushed prior to network
975 * Utilize Win32 DNSQuery API instead of internal routines. This
976 allows DNS SRV queries to be sent to all current domain name
977 servers. Not just one specified in an INI file. DNS is now
980 * "NetbiosName" registry value may be used to specify a fixed
981 Netbios Name such as "AFS" to be used instead of "HOSTNAME-AFS"
982 when the loopback adapter is in use. If you need to use the
983 old notation with a loopback adapter installed specify a registry
986 "NetbiosName" REG_EXPAND_SZ = "%COMPUTERNAME%-AFS"
988 * Refactor all modules which depend on LAN Adapter and NetbiosName
989 determination in a new library: lanahelper.lib. This allows for
990 consistent behavior throughout the product.
992 * Move the afsd.log and afsd_init.log files to the directory specified
993 by the "TEMP" environment variable. This is usually %WINDIR%\TEMP
994 for services. Added the Date to the log entries.
996 * New registry value "RxMaxMTU" used to limit the size of the RX
997 packets sent by the AFS Client Service to the Server. In order
998 to enable OpenAFS to work across the Cisco IPSec VPN the packet
999 size must be restricted to 1264 or smaller. The latest NSIS
1000 installer sets a value of 1260 by default.
1002 * New registry value "RxNoJumbo" to disable the use of Jumbo Rx
1003 packets. This is not needed in order to work across the Cisco
1004 VPN but might be needed for other network environments. This
1005 value is not set by the NSIS installer.
1007 * New registry value "HideDotFiles" is used to apply the Hidden
1008 attribute to files whose names begin with a '.'. This value
1009 is set by the NSIS installer.
1011 * New registry value "MaxMpxRequests" allows the maximum number
1012 of multiplexed sessions to be configured at run time. This
1013 value is not set by the NSIS installer. The default value is
1016 * New registry value "MaxVCPerServer" allows the maxmimum number
1017 of VCs per server to be configured at run time. This value is
1018 not set by the NSIS installer. The default value is 100.
1020 * New registry value "AllSubmount" allows the "all" submount to
1021 be disabled by setting its value to 0x00.
1023 * Allow cells names to be valid mount points
1024 \\<netbiosName>\<cellname>
1026 * Store the active state of drive mappings in order for afscreds.exe
1027 to restore them upon startup
1029 * Add exception handling to generate a Stack Trace to the afsd_init.log
1030 file if one happens to occur.
1032 * Add lots of logging to help detect the cause of invalid SMB packets
1034 * Enable Kerberos for Windows to be used to obtain AFS Tokens via
1035 conversion of Kerberos 5 "afs" service tickets. Supports auto-
1036 renewal of expiring tokens as long as afscreds.exe is running.
1038 * New afscreds.exe command line options:
1040 -M = renew drive maps
1041 -N = ip address change detection
1044 * New registry value "EnableKFW" in {HKCU,HKLM}SOFTWARE\OpenAFS\Client
1045 determines whether or not MIT Kerberos for Windows should be used
1046 to obtain tokens via Kerberos 5 tickets.
1048 * New registry value "AfscredsShortcutParams" in
1049 {HKCU,HKLM}SOFTWARE\OpenAFS\Client
1050 determines the command line parameters to be specified when "fixing"
1051 the AFS Shortcut in the user's startup folder.
1053 * The "ShowTrayIcon" registry value has been moved from
1054 HKLM\Software\TransarcCorporation\AFS Client\AfsCreds to
1055 {HKCU,HKLM}SOFTWARE\OpenAFS\Client
1057 * The <cell name> registry values used to store the token expiration
1058 reminders have been moved from
1059 HKLM\Software\TransarcCorporation\AFS Client\AfsCreds to
1060 {HKCU,HKLM}SOFTWARE\OpenAFS\Client\Reminders
1062 * Obtain the Logon User Name from the Explorer key when available
1064 * new text document doc\txt\winnotes\registry.txt lists all registry
1065 values used by OpenAFS (excluding the AFS Server)
1067 * BUG: rx_securityClass objects were not properly reference
1068 counted and were never freed.
1070 * BUG: reduce the number of conditions under which CM_ERROR_TIMEOUT
1071 would be generated. The existence of a server does not imply
1072 that it is not down. If all of the servers for a cell are down
1073 return CM_ERROR_NOSUCHVOLUME instead. This prevents the Explorer
1076 * BUG: the directory name lookup cache failed to free the entries
1077 in the cache when the name cache entries cycled. The entries
1078 in the cache would become dereferenced without being freed.
1080 * BUG: fs setserverprefs could be executed without Administrator
1083 * BUG: the number of allocated NCB objects (100) exceeded the number
1084 which could actually be waited upon by the kernel (64). Any objects
1085 which were utilized above the limit could never have event completions
1088 * BUG: smb_username_t objects were not being reference counted and
1089 were not properly freed.
1091 * BUG: smb_tid_t objects could under unusual circumstances be freed
1092 before they were no longer referenced.
1094 * BUG: smb_fid_t object pointer were frequently used even when
1095 their value could be NULL. They were not properly released and
1096 therefore they were never freed.
1098 * BUG: smb_packet_t data structures were not completely initialized
1101 * BUG: when Rx produces a CM_ERROR_NOIPC error do not return "Access
1102 Denied" because that causes the Explorer Shell to try again until
1103 access is obtained. Instead return "Remote Resources" which allows
1104 the shell to move on and treat the error as transient.
1106 * BUG: when initializing the NCBreturns structure, separate Event objects
1107 were created for each NCB although a single Event object was supposed
1108 to be shared by all.
1110 * BUG: smb_dirSearch_t objects were not being properly referenced counted
1113 * BUG: smb_tran2Packet_t objects were not being properly referenced
1116 * BUG: directory path creation did not handle the case of multiple
1117 directories requiring creation in one attempt
1119 * BUG: SMB requests which required an Extended Response were ignored.
1120 This prevented some files from being written to AFS volumes.
1122 * BUG: character strings were being freed even after they were
1123 inserted into in use data structures
1125 * BUG: inconsistent usernames were used when High Security mode was
1126 enabled. (there is still much to do in this area)
1128 * BUG: pioctl() calls which require out of band RPC operations were
1129 susceptible to race conditions when performed by multiple processes
1131 * BUG: memory allocation and deallocation crossed instances of the
1132 C Runtime Library producing memory leakage and corruption in
1133 afscreds and the client configurator.