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