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