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