3 * Fix the code that reads the backconnnectionhostnames value
4 so that there is not an uninitialized variable
8 * integrated logon could cause winlogin.exe to blue screen windows
9 if it was called with a domain that does not exist on the machine.
10 this is possible during a sysprep.
12 * corrections to cm_buf_t handling to ensure that buffers are
13 removed from queues before they are freed and that holds are
14 obtained on the next buffer in a chain before releasing the
17 * do not generate MessageBox dialogs on network errors. they
18 cause more trouble then they are worth.
20 * move GlobalAutoMapper into a separate thread so that it does
21 not prevent service startup if the WNetAddConnection2 call
24 * restrict hard dead and connection timeouts to the CIFS Session
25 Timeout value. This is being done to try to prevent virtual
26 circuits from being destroyed prematurely.
28 * Fix the code that writes the backconnectionhostnames value
29 to ensure that the data buffer is written with the correct
32 (there were no windows specific changes between 1.5.4 and 1.5.5)
36 * Corrections to the Integrated Logon functionality that permits
37 Kerberos 5 TGTs to be communicated into the user session. The
38 transfer is now more secure and succeeds when the user does not
39 have read permission to the %SystemRoot%\TEMP directory.
41 * NSIS installer updated to version 2.18
43 * WiX installer updated to version 2.0.4221.0
45 * Updates to the IFS functionality for 64-bit correctness and
46 permit compilation. The IFS functionality works for pioctl()
47 operations but not much else at this point.
49 * A major re-write of the OpenAFS implementation of the CIFS Tran2
50 query and set functions.
52 * Ignore the Windows CIFS client session timeout entirely. Timeout
53 only after the AFS Hard Dead Timeout period expires.
57 * move headers, libraries, and samples from OpenAFS\Client to
60 * remove the auto-registration of AFS IDs for foreign cells
61 from integrated logon. this permits afslogon.dll to avoid
62 initializing the RX library. afslogon.dll is a network
63 provider library and as such it is loaded into all applications
64 which perform a CreateProcessAsUser call. Initializing the
65 RX library spawns background threads to listen for inbound
66 packets. When the network provider is unloaded from the
67 process, the RX library does not cleanup the threads. If they
68 continue to execute after the library is unloaded, the process
71 * implement inline bulk status calls. this will significantly
72 improve the performance of directory listings.
74 * prevent a crash when evaluating mountpoints to volumes that do not
77 * new command: fs uuid [-generate]
78 displays the current uuid and allows a new one to be generated
79 on the fly without restarting the afs client service.
81 * fix the 64-bit installers to properly document the install
84 * move help files to the proper location so they can be located by
85 the system tray tool and the control panel.
87 * "over quota" and "disk full" errors were not being reported to the
90 * largefile support has been added. Files greater than 31-bits can no
91 longer be written to file servers which do not support large files.
92 When file servers support large files, files up to 64-bits can be
95 * cm_SyncOp could return with the input buffer unlocked upon error
96 which would result in a panic condition. This bug was introduced
99 * vlserver failover when freelance mode did not work. This prevented
100 the root.afs volume from being loaded if the first vlserver could
105 * A bug in the CIFS Standard Info response packet caused directories
106 to appear as standard files. This prevented Microsoft Vista from
107 being able to walk the AFS directory tree.
109 * Mount points must be reported as directories in response to
110 Query Path Info operations.
112 * A deadlock was detected when performing "fs flushall" if the
113 file server reports VNOVNODE. The scp->createBufferLock is
114 already held by the current thread and there is no mechanism
115 to propagate the knowledge. Therefore, an alternate mechanism
116 for clearing the cache must be developed. A new function
117 cm_RecycleSCache(scp,flags) has been extracted from
118 cm_GetNewSCache(). This function performs the task of recycling
119 an cm_scache_t object. When called from cm_GetNewSCache() with
120 no flags the expectation is that there are no associated buffers
121 that are queued to be read or written. When called from
122 cm_Analyze() with the CM_SCACHE_RECYCLEFLAG_DESTROY_BUFFERS
123 flag, any queued buffers will be de-queued and marked as if
124 the operations were performed so the data can be discarded.
126 * CM_ERROR codes were logged as "unknown" by cm_Analyze.
128 * In response to VNOVNODE, the parent is only discarded if the current
129 cm_scache_t is not a directory.
131 * In the Ioctl FlushFile and FlushVolume functions, there were no
132 checks to protect against flushing the Freelance SCache entries.
134 * In FlushFile, the wrong cm_scache_t object was being released.
136 * In cm_GetNewSCache, do not allow Freelance SCache entries to be
137 recycled. Choose a new entry if cm_RecycleSCache fails.
139 * Speed up the performance of the cache manager by not
140 holding the smb_fid_t mutex across calls to cm_SyncOp
143 * Ensure that all smb_fid_t flag references are protected.
145 * Remove a deadlock between smb_fid_t mutex and
146 smb_rctLock introduced in 1.4.1.
148 * Fix aklog AFSID lookup to use not send the realm
149 name when the realm is the local realm for the
150 cell. The PT Server doesn't strip the realm
151 name when it is the local realm.
153 * Treat "\\afs\*." as an alias for "\\afs\all"
155 * Dynamically adjust the priority of server threads
156 based upon the age of the CIFS request that is
157 being processed. The priority is bumped one level
158 for every 15 seconds of processing time.
160 * The original openafs contribution mis-used the
161 cm_GetCallback function. This function should only
162 be called as a side effect of a call to
163 cm_SyncOp(CM_SCACHESYNC_NEEDCALLBACK). The way it
164 was being called results in a FetchStatus RPC being
165 performed even when the client already has a valid
166 callback and does so in a manner that destroys the
167 synchronization of the threads that are calling
168 cm_SyncOp. If nothing else this results in a
169 significant performance penalty.
171 * More changes to cleanup of smb_vc_t objects in
172 order to prevent race conditions.
174 * Reduce the amount of Power Management event logging
177 * If the client detects that the IP address has
178 changed, force the use of new RX connections. This
179 enables the file server to recognize that the client
182 * Remove a race condition and deadlock associated
183 with cleanup of smb_vc_t objects.
185 * Fix the ANSI filename support. One function that
186 required it was missing the translations.
188 Changes not present in 1.4.1 and since 1.5.0: 1.5.1 released
191 * Add a DllMain() function to afspthread.dll. Perform
192 cleanup of thread local storage, rx queues, critical
193 sections, event handles, etc. This was implemented
194 to avoid crashes in afspthread.dll when applications
195 which load/unload the dll attempt to terminate.
197 * Lock request behavior has been altered. As of this
198 release a locally allocated lock will be used whenever
199 the volume is RO or the requesting user's permissions
200 are 'rl'. This will allow end users to execute programs
201 from RW volumes when they do not have the 'k' privilege.
203 Note that a recent discovery indicates that the 'k' bit
204 is only supposed to control the ability to obtain read
205 locks. Write locks are to be controlled by the 'w' and
208 * Code has been added to enable the cache manager to be
209 able to obtain the AFSID of the authenticated user.
210 This is required to be able to determine when "Insert"
211 privileges should apply. AFS considers a file to be
212 a new file whenever the owner's AFSID matches the
213 AFSID of the user. The current implementation relies
214 on the name specified during the SetToken call to be
215 correct. This will be replaced in the future with a
216 new RPC that allows the AFSID of the authenticated
219 * A 32-bit-tools installer for use on 64-bit systems
220 is now available. These tools are for use with 32-bit
221 versions of Kerberos for Windows or JPSoftware's 4NT.
223 Since 1.4.1 rc10: 1.4.1 final released (9 April 2006)
225 * Remove the use of the "active_vcp" variable. This variable
226 no longer serves any useful purpose and was the cause of
227 race conditions that produced under counts of the smb_vc_t
230 * Change default minidump output to include data segments
232 * restore access to cm_IoctlGetVolumeStatus and
233 cm_IoctlSetVolumeStatus calls for AFS pioctl operations.
234 Still need to figure out why they are being called
235 for SMB/CIFS IOCTL operations instead of Trans2GetFileInfo.
237 Changes not present in 1.4.1: 1.5.0 released (16 Feb 2006)
239 * Update build system to include the "sys_name" in the
242 * optimize the number of calls to obtain the smb_user_t for a
245 * add logging of server addresses, status and capabilities when
248 * prevent multiple threads from pinging the same server simultaneously.
249 instead, threads block and then use the result of the ping that was
250 already taking place.
252 * Add registry values to allow the defaults for daemon checks to be altered
253 at startup. Log values to afsd_init.log.
255 daemonCheckDownInterval
256 daemonCheckUpInterval
257 daemonCheckVolInterval
258 daemonCheckCBInterval
259 daemonCheckLockInterval
260 daemonCheckTokenInterval
262 * Add EventLog messages for transitions in fs crypt state.
264 * Byte range locking (when locks will be obtained from the
265 is still under discussion)
267 * 64-bit Windows operating systems now supported
268 (XP SP2 64-bit, 2003 SP1 64-bit, 2003 R2 64-bit)
269 This is a native 64-bit implementation of OpenAFS for Windows.
270 There is currently no 64-bit version of KFW and therefore
271 there is no (easy) method for obtaining AFS credentials.
272 32-bit KFW 3.0 can be used with 32-bit OAFW libraries
273 to obtain AFS tokens but there is not for the feint of
276 * A faster implementation of the fcrypt algorithms improves
279 * The afsd_service.exe now supplies Event Log Message Text.
280 The event log no longer generates warning text due to lack
281 of message configuration.
283 * When afs servers are unreachable and network stack returns
284 a WSAEHOSTUNREACHABLE error, the AFS client will immediately
285 mark the attempted server as being down. This allows for
286 very fast response to the calling application. This change
287 has a pronounced improvement when the Windows Explorer is
288 used on disconnected mobile computers.
290 * Added DebugOutputString debugging of the RX library
292 Since 1.4.1 rc9: 1.4.1 rc10 released (10 March 2006)
294 * Fix the rx-lwp implementation to randomly generate rx call
295 identifiers which are supposed to be unique at a given point
296 in time. This affects some of the command line tools used
297 for debugging but not the AFS Client Service itself which
298 uses the rx-pthreads implementation.
300 * xstats_fs_test.exe and xstats_cm_test.exe are now built for
301 Windows although they are not distributed
303 * don't generate an exception when logging unexpected SMB packets
305 * the data structures used by cm_IoctlGetVolumeStatus and
306 cm_IoctlSetVolumeStatus are not compatible with the CIFS
307 Get/Set File Information calls so don't bother executing them.
311 * Fix data written to registry as part of BackConnectionHostnames
314 * Fix initialization bug when allocating cm_server_t objects that
315 would cause servers to appear to be down after each allocation
316 or renewal. Server would appear up after the next check servers
321 * Windows will return WSAECONNRESET to the next receive packet
322 operation on a socket if an ICMP packet is received in response
323 to a packet that was sent and could not be delivered because
324 the port was unreachable. We have to treat this as
325 WSAEWOULDBLOCK so that we can retry the select() check and
326 not mark the connection as bad.
328 Since 1.4.1 rc6: 1.4.1 rc7 released (14 Feb 2006)
330 * The client manager maintains a least recently used list of
331 all the ACLs. If an ACL is already the most recently used
332 do not bother to remove it from the list and place it on the
335 * As part of the process of adding a new server, set the
336 server is down flag and then perform a ping. If the server
337 is up, the flag will be reset. If the server is down, the
338 client will not timeout unnecessarily while attempting to
341 * If a Mountpoint String is the empty string, return PATH NOT
344 * Modify behavior of the Network Provider to avoid querying the
345 profile location if integrated logon is known to be disabled.
347 * Correct behavior of 'LogoffPreserveTokens'. When set, tokens
348 will always be preserved regardless of whether or not integrated
349 logon was used to obtain tokens. When unset, tokens will be
350 destroyed regardless of whether integrated logon was used to
351 obtain the tokens unless the profile is stored in AFS.
353 * Disable LogoffTransferToken functionality. The SMB V3 Logoff
354 message is being delivered even when the user is not logging
357 * Fix a deadlock condition introduced in rc6.
359 * Cell names are case-insensitive. Since the founding of OpenAFS
360 there has been a bug that treated "cell", "Cell", and "CELL" as
361 different cells. This would result in what appeared to be
362 random disappearance of user tokens or a failure to authenticate
363 even when tokens were listed by the "tokens" command.
365 Since 1.4.1 rc5: 1.4.1 rc6 released (2 Feb 2006)
367 * Additional auditing of the smb code revealed that smb ioctl
368 operations were failing to free smb_fid_t objects
370 * The File Identifiers assigned to smb_fid_t objects could be
371 given the value 65535 which is 0xFFFF which is also the
372 INVALID_HANDLE value. Both 0 and 65535 are now treated as
375 * Audited all assignments to fields and ensured that they are
376 protected by obtaining the relevant mutex object.
378 * Re-wrote the VNOVNODE handling to avoid a potential deadlock
379 if both the current cm_scache_t object and its parent are
380 both returning VNOVNODE.
382 * Removed all the logic associated with the 'dead_vcp' variable
383 which must have been added for debugging because its used
384 was never thread safe and it truly served no purpose.
386 Since 1.4.1 rc4: 1.4.1 rc5 released (18 Jan 2006)
388 * Check access permissions to the file before the file is
391 * More improvements to the handling of SMB Virtual Circuits
392 when SMB sessions are closed.
394 * Correct a race condition introduced in rc4 that could result
395 in a crash of afsd_service.exe.
397 Since 1.4.1 rc3: 1.4.1 rc4 released (11 Jan 2006)
399 * Properly handle pre-mature SMB session closures.
400 File handles, tree connections, and user sessions are now
401 freed when the virtual circuit is closed.
403 * smb_username_t and smb_user_t objects are now properly reference
404 counted and freed as appropriate.
406 * disable to use of AFS file locks. byte range locking is still
407 implemented but all locks are managed locally. This prevents
408 multiple processes from editing the same file on the same
409 machine but it does prevent multiple processes on separate
410 machines from modifying the file.
412 Since 1.4.1 rc2: 1.4.1 RC3 released (4 Jan 2006)
414 * A fix to "fs setserverprefs -vlserver". Multiple calls with
415 the same server parameter would result in a panic condition
416 if the server had not already been contacted by the AFS
419 * Better warnings are written to the afsd.log file when
420 the Windows RPC Protocols are not properly configured as
421 is often the case on Windows 2000.
423 * fix the procmgmt library to restore C RTL signal handlers when
424 it is being detached from the process prior to process termination.
426 Since 1.4.1 rc1: 1.4.1 RC2 released (30 Nov 2005)
428 * close a lock leak in the rx library that could be triggered while
431 * prevent removal of drive mappings in response to afscreds.exe -M
433 * add logic to process VNOVNODE in cm_Analyze. Force re-evaluation of symlink
434 strings and flush the stat cache entry.
436 * prevent server objects from being freed if user preferences are set.
438 * Update WIX support to 2.0.2419.0
440 * Release all locks on the server at service shutdown.
442 * A down server should be marked up as long as it responds to the client.
443 It doesn't matter if the server returned an error as long as the error
444 is something other than VRESTARTING. If there is such an error, all
445 connections on that server should be marked for replacement.
447 * Change the check "up" servers period from once per hour to once every
448 ten minutes. This matches the behavior of the Unix cache manager.
450 Post 1.4.0 revisions: 1.4.1 RC1 released (21 Oct 2005)
451 * Byte Range Locking support has been added. Architectural documentation
452 is located within src/WINNT/afsd/cm_vnodeops.c. Best efforts are
453 made to enforce Windows mandatory locking model using locally managed
454 byte range locks with full file locks obtained from the file server.
455 Read-only volumes provide the user with an implied locking privilege.
456 Read-write volumes require that a user be granted the locking privilege
457 in order for a lock to be obtained. As most Windows applications use
458 Shared file access modes, they require the ability to obtain locks in
459 order to access files.
461 * Implement error translation functions to convert Universal Error Codes
462 output by modern servers to local errno and winsock error values.
463 This fixes the error message problems using pioctl() calls from fs.exe
464 and the AFS Shell Extension.
466 Since 1.4.0 rc8: 1.4.0 final tagged (20 Oct 2005); released (31 Oct 2005)
467 * Allow the AFS Client Service to set the firewall configuration by
468 retrying until after Windows determines the boot period is over.
470 * Do not attempt to configure the firewall on Windows 2000, XP pre-SP2,
473 * Detect IP address changes from within the AFS Client Service for the
474 purpose of checking down servers sooner
476 * If the file server or vldb server report RXKADUNKNOWNKEY, return
477 SEC_E_NO_KERB_KEY to Windows. This provides an indication to the
478 user that there is a Kerberos key problem. Previously the user would
479 receive no feedback when there was something wrong.
481 * Fix the large integer library support to properly handle values greater
484 Since 1.4.0 rc7: 1.4.0 rc8 released (15 Oct 2005)
487 * Fixed file name pattern matching. Question marks can match nothing
488 if found at the end of a component.
490 Since 1.4.0 rc6: 1.4.0 rc7 released (8 Oct 2005)
491 * Kerberos 5 ticket lifetimes should adhere to KFW Leash lifetimes
493 * The MSI installer now has a new Product ID for each build. This
494 is to allow for automated upgrades. The Upgrade ID is remaining
497 * Volumes that were cached and then subsequently were salvaged,
498 moved or otherwise taken temporarily offline (as opposed to being
499 busy) would become unreachable. A distinction is now made between
500 a volume being offline and a server being down.
502 Since 1.4.0 rc5: 1.4.0 rc6 released (2 Oct 2005)
504 * Fixed several AFS Shell Extension issues:
505 - Checking Server Status would only work if a specific cell was
507 - If servers were down, the Server Down dialog would write to
508 invalid memory and cause explorer.exe to crash
509 - Default Push Buttons were not specified for many dialogs
510 - The extension would be unloaded by the Explorer Shell and
511 never be reloaded under some circumstances.
513 * Fixed the AFS System Tray menu to disappear if another Window
514 was selected before a menu item was selected
516 * Added volume owner and group information to "fs examine" output
518 * Added fs and registry support for enabling/disabling/clearing
519 rx statistics gathering.
521 Since 1.4.0 rc4: 1.4.0 rc5 released (25 Sep 2005)
523 * New Product Code GUIDs issues for 1.4 and 1.5 branches. Separate
524 GUIDs for each platform.
526 * Documentation directory structure and default installation rules
529 * New OpenAFS for Windows HTML Release Notes installed
530 as part of the documentation set.
532 * Add thread id to rx debugging messages
534 * When all servers are offline, return a bad network path error
535 immediately. This is necessary to allow Explorer to do the
536 right thing and not hang. The background daemon thread will
537 check the down servers every 30 seconds to see if they are
540 Since 1.4.0 rc3: 1.4.0 rc4 released (14 Sep 2005)
542 * The AFSCache file has been modified to store both the
543 serial number of the volume on which the file resides
544 and the SID of the local machine. If either change,
545 a new UUID is generated.
547 * add "fs flushall" command that forces all data buffers
550 Since 1.4.0 rc2: 1.4.0 rc3 released (4 Sep 2005)
552 * add support for '/' instead of '\' in pioctl() calls
554 * Apply AFS Client Admins group protect to AFS Shell Extension
556 * Add support for \\afs\<name> to most AFS Shell Extension
557 commands except the symlink methods.
559 * when installing the Microsoft Loopback Adapter, enable
560 MS Client for Networks and prevent an install failure
561 by not calling CoInitialize twice in the same thread.
563 * reload cell vldb values from the CellServDB every two
564 hours in case it changes
566 * When updating cell information from DNS, be sure to set
569 * Add support to allow use of \\AFS\<foo> where <foo> is
570 either a mount point or symlink. As <foo> is normally
571 treated as a share name, we transform it into \\AFS\all\<foo>
574 * Init 'code' to prevent false errors when integrated logon
575 is disabled and the service is not running
577 Since 1.4.0 rc1: 1.4.0 rc2 released (28 Aug 2005)
579 * Removed trace log messages that were hampering performance.
581 * Fixed a deadlock that was being triggered by editing Word
582 documents stored within AFS with WinWord 2003.
584 * Bit 3 of the TraceOption registry value is now used to set the
585 default for "fs trace" in the non-Debug builds. The new default
586 is off for release builds and on for debug builds.
588 * Bit 2 of the TraceOption registry value can be used to turn on
589 real-time output of debug log entries to the Windows Debug
590 Output monitor interface. This data can be viewed with tools
591 such as Sysinternal's DbgView.
593 Since 1.3.87: 1.4.0 rc1 released (17 Aug 2005)
594 * When the cache manager reports ALLBUSY or ALLOFFLINE for
595 a resource we should not be returning status codes such
596 as Network Busy or Remote Host Down because these errors
597 will imply that the AFS Client Service is Busy or Down
598 and that is simply not the case. Instead we will return
599 Bad Network Path as the path is temporarily not available.
601 Instead of returning Sharing Paused when there is a
602 timeout error, return Timeout. Once again, the AFS Client
603 Service is not paused.
605 * afscreds.exe would display an Obtain Creds dialog when
606 the expired credentials reminder was triggered even
607 if there was no network path to the KDC. This is prevented
608 by adding KDC probe logic to the reminder thread.
610 * afscreds.exe would display expired tokens no differently
611 than unexpired ones. This would make it difficult for the
612 user to distiguish when the tokens were expired. For the
613 English build added a new resource string "(expired) that
614 is displayed instead of the expiration time.
617 * "fs wscell" when executed in freelance mode will return the
618 name of the cell configured in the registry. The root.afs
619 volume is not loaded from this cell, but it is used for the
620 default for aklog and integrated login.
622 * "fs mkmount, fs rmmount, symlink make, symlink remove" will
623 no longer work on \\AFS\all when freelance is being used
624 unless the user is a member of the "AFS Client Admins" Windows
627 * some more checks performed during persistent cache validation.
630 * Optimize calls to cm_CheckServer from cm_Analyze. Only check
631 down servers for the current cell not all cells.
633 * If the scache LRU list becomes corrupted, the AFS Client Service
634 might enter an infinite loop at startup. Detect the corruption
635 and discard the cache contents in this case.
637 * Fixed the Explorer Shell's remove mountpoint functionality.
639 * Fixed a deadlock caused by the holder of cm_aclLock attempting to
640 obtain a mutex lock on a cm_scache_t object whose lock is held by
641 a thread attempting to obtain the cm_aclLock.
644 * Really fixed DNS AFSDB queries to ensure that "csail" cannot be
645 misinterpretted as "csail.mit.edu" when the resolver
646 is configured to append ".mit.edu" to failed DNS queries.
648 * Added a new registry key, "LogoffPreserveTokens" (see registry.txt),
649 that can be used to force the preservation of user tokens upon logout.
651 * Update the NSIS install scripts to use NSIS 2.07. This release adds
652 recommended installation categories: AFS Client, AFS Administrator,
653 AFS Server, AFS Development Kit. Each category includes a different
654 default subset of the OpenAFS components.
656 The OpenAFS logo is now associated with the NSIS uninstall entry
657 in the Add/Remove Programs control panel.
659 * The user name associated with AFS tokens when obtained with
660 integrated login, the afs systray tool, or aklog will always
661 include the full Kerberos 5 user principal name regardless of
662 whether or not the cell is local to the realm.
664 * Modify integrated login so that it does not enter an infinite
665 loop if the service is not set to auto start.
667 * Added asetkey.exe used to set a Kerberos 5 key for use by the
670 * Added uninstall.exe to Wix installation
672 * More modifications to algorithms used to wake sleeping threads.
676 * Changes to the algorithms used to wake threads when they are
677 put to sleep because of conflicts over buffer operations.
680 * The OpenAFS integrated logon obtains Kerberos 5 tickets as part of
681 the process of producing AFS tokens. The tokens are stored within
682 the AFS Client Service but the Kerberos 5 tickets have been discarded.
683 New functionality has been added to temporarily copy the tickets to
684 a file ccache during the short window between the NPLogonNotify and
685 WinLogon Logon Event. The Logon Event handler starts a process as
686 user, afscpcc.exe, that copies the tickets into the default ccache.
687 The file ccache is then destroyed by the event handler.
689 * During synchronization operations on stat cache entries, if threads
690 are forced to sleep it was possible that the threads would not be
691 woken under heavy load.
693 * Enforce the delete on close flag specified by the NTCreateX()
696 * A race condition in the rx library was fixed that resulted in
697 a deadlock in rx_NewCall when the RX_CONN_MAKECALL_WAITING flag
698 was cleared when threads were still waiting to use the
699 connection. Also, fixed a potential case in which the
700 connection could be destroyed while threads were waiting to use it.
702 * The DNLC freelist has been seen to become corrupted with still
703 active entries being stored on the freelist. Changes were made
704 to perform a better job of cleaning entries before placing them
705 onto the freelist; marking them with the correct magic value when
706 purging the list; and allowing the list to be purged on startup
707 if the cache validation fails.
709 * Windows Crash Reporting does not get triggered for afsd_service.exe
710 because it provides its own top level exception handler. This patch
711 places an explicit call to ReportCrash() on platforms which support
714 If you configure Crash Reporting via AD Policy to capture crash
715 reports within the domain, then you will receive this output.
717 * Generate MiniDumps independent of the Windows Crash Reporting.
719 (a) If an exception occurs,a minidump will be generated at the path
720 %TEMP%\afsd.dmp. The type of minidump defaults to Normal but
721 can be set to any other type via use of the
724 [HKLM\SOFTWARE\OpenAFS\Client] MiniDumpType (DWORD)
726 (b) MiniDumps can be generated at any time using the "fs minidump"
727 command. This allows you to generate a minidump without
728 stopping the process or even requiring the use of a debugger
731 * an RX connection which reports bad ticket now treats it the same way
732 the expired ticket is treated. The ticket is removed from the
733 connection and a new anonymous connection is established.
735 * fs memdump now requires that the caller be in the AFS Client Admins
738 * additional debugging information is provided in cm_Analyze when the
739 error code is ignored.
741 * Fix a regression introduced into the pioctl() client code which
742 will cause a crash in winlogon.exe, explorer.exe and fs.exe if
743 MIT KFW is not installed. (1.3.82a)
745 * Remove AFS Gateway option from OpenAFS Control Panel (1.3.82a)
748 * Fix a race condition in cm_EndCallbackGrantingCall() that
749 could leave 'nrevp' pointing to freed memory. In the process,
750 optimize the processing to ensure that the applications monitoring
751 the status of the stat cache entry are only notified at most
754 * Conditionalize access to the Explorer Shell AFS->Mount Point
755 ->Remove menu item. Disable the item if the selected item(s)
756 are not mount points.
758 * Activate AFS RPC (RX) Free Packet Queues stored in Thread
759 Local Storage. This eliminates thread contention on the
760 global RX free packet queue. This should improve performance
761 on multi-CPU systems.
763 * Fix the IP address filtering code to properly load/unload
764 the IPHelper DLL so that Windows XP/2003 and beyond systems
765 do not have to manually probe the registry.
767 * CleanupACLEnt() was not being called consistently with
768 the cm_scache_t object referred to by the back pointer
769 mutex locked. This could in very rare conditions lead to
770 an invalid memory access.
772 * Added a script command to the msi installer "afs_replace"
773 which can be used to replace one version of OpenAFS with
774 another without requiring an uninstall and reinstall if
775 the installed msi is no longer in its original location.
777 * Apparently the problem with multi-domain forests with cross-
778 realm trusts to non-Windows realms was not entirely solved.
779 The authentication to the AFS SMB service failed because
780 the wrong name was being used. Using ASU as an example,
781 the authentication was being performed with the name
782 "QAAD\user" (an account in the forest root) and not
783 "user@ASU.EDU (the MIT Kerberos principal used to login with)
785 The solution was to add an additional dependency on KFW
786 in order or to be able to easily obtain the client principal
787 name stored in the MSLSA ccache TGT. This information is
788 used in two locations:
790 - the pioctl() function
792 - a new WinLogon Event Handler for the "logon" event.
794 The pioctl function will now be able to use the correct
795 name when calling WNetAddConnection2() and the "logon"
796 event handler will now be able to call WNetAddConnection2().
797 The hope is that the "logon" event handler will be called
798 before the profile is loaded but I have not guarrantee
802 * Fixed a locking error in cm_TryBulkStat() which had the
803 potential of deadlocking the system for the length of time
804 it takes to perform a bulk status fetch operation.
806 * Replaced time conversion code (UnixTime <-> FILETIME) to
807 be completely arithmetic instead of relying on a bizarre
808 algorithm involving a variety of C RTL time functions.
809 This has the side effect that UnixTime and FILETIME which
810 are both stored in UTC are interpretted as UTC throughout
811 the year. Windows will apply the same localization to AFS
812 as it does to NTFS. Applications which rely on the ability
813 to sync files between the two file systems will no longer
814 see the timestamps of files in AFS change an hour relative
815 to the files stored in NTFS or Windows based backup devices.
817 * Fixed a invalid memory access under a bizarre circumstance.
818 Windows will allow a physical mass media device to be
819 installed via Plug N Play to the system and will assign it
820 the lowest available drive letter. This is true even if the
821 drive letter is currently assigned in the user session to
822 a network device via NET USE (or its equivalent.) When this
823 happens, queries sent to the CIFS server will contain invalid
824 data. This invalid data was not being caught by the AFS
825 Client Service and was resulting in a crash when Freelance
828 * Fixed a reference count error when registering callbacks
829 on a stat cache object if the callback was already registered
831 * Add a case to cm_Analyze() in order to handle the case where
832 cm_GetConnByMServers() returns CM_ERROR_NOSUCHVOLUME because
833 the server list for the volume is empty. In this case, force
834 an update of the volume info and retry.
836 * Insert a missing cm_EndCallbackGrantingCall() which could
837 result in threads waiting for a callback to complete to never
840 * In the persistent cache, there is a maximum number of volume
841 entries. Allow volume entries to be reused if the maximum
842 number have been allocated and their reference count is zero.
844 * If we already have a dead virtual connection object, don't
845 ignore the fact that additional dead vc objects must be taken
848 * Removed a deadlock condition introduced in the summer of 2004.
849 Do not hold mx locks around calls to RX functions including
850 rx_NewCall(). That is what reference counts on the rx_connection
853 * Fixed an initialization error in afslogon.dll which could
854 result in random behavior including a failure to terminate
855 the NPLogon function. (1.3.80b)
857 * Fixed an error preventing the use of SMB authentication
858 on Windows 2000. (1.3.80a)
861 * Updated CellServDB to Public CellServDB 16 Mar 2005
863 * Fixed DNS AFSDB queries to ensure that "csail" cannot be
864 misinterpretted as "csail.mit.edu" when the resolver
865 is configured to append ".mit.edu" to failed DNS queries.
867 * Fixed another case in which the client would replace connections
868 to the host when it was not necessary. In this case the
869 situation would occur if cryptall was on and the connections
870 were unauthenticated due to lack of an appropriate token.
872 * OpenAFS for Windows has failed to work at sites which are
873 utilizing a cross-realm trust between an MIT/Heimdal realm
874 and a multi-domain Windows forest when the workstation being
875 accessed is not located in the root domain. This is caused
876 by a bug in the workstation which was triggered after the
877 introduction of Windows 2003 Server. When the bug is triggered,
878 the workstation attempts to authenticate users to afsd_service.exe
879 by contacting the Domain Controller instead of using the
880 LSA loopback authentication mechanism.
882 One of the reasons this bug occurs is because the workstation
883 does not have a reliable way of knowing that the service whose
884 netbios name is "AFS" is located on the workstation. This will
885 be fixed starting in Longhorn Beta 1 by Microsoft. The
886 "BackConnectionHostNames" registry value will be used to
887 indicate that the authentications to that service name should
888 be performed using the loopback authentication mechanism.
890 In the meantime, when Logon Caching is enabled, we can force
891 afsd_service.exe to authenticate using the logon cache before
892 contacting the Domain Controller. This will work with both
893 password and smart card based logons.
895 * The allDown logic in cm_ConnByMServers() was wrong. The allDown
896 flag should not be cleared if a volume's server reference is
897 marked as "offline". In the case where all of the volume's
898 servers are either "down" or the volumes are "offline", we want
899 cm_Analyze() to process the condition as CM_ERROR_ALLOFFLINE
900 instead of as CM_ERROR_TIMEDOUT. In fact, CM_ERROR_TIMEDOUT
901 should never occur in practice.
903 In the case of CM_ERROR_ALLOFFLINE, cm_Analyze() will sleep for
904 5 seconds, clear the server down and volume busy flags, and
905 then force an update from the VLDB. This allows the client to
906 update the location of a volume if the reason for it being
907 marked offline is because it is being moved. Calls to
908 cm_ConnByMServers() will be retried either until success or
909 the RDRtimeout period is reached.
911 * Correct the Power Management code behavior in response to
912 Standby, Suspend, and Shutdown events. Instead of flushing the
913 buffers associated with the mounted SMB submounts, simply write
914 all buffers which are marked dirty.
916 * Added support for "TheseCells" to afslogon.dll. "TheseCells"
917 provides a list of cells other than the default cell for which
918 tokens should be obtained using the default Kerberos principal.
919 This functionality is logon domain specific and is only available
920 when using KFW for authentication.
922 * Fixed FindNext Invalid Handle error caused by over agressive
923 attempts at garbage collecting dirSearch entries when the
924 dirSearch ID wraps from the maximum value to 1.
926 * Add support for registry defined server preferences for VLDB and
927 File servers. See registry.txt for details.
929 * Increased default cache size to 96MB and default number of cache
932 * Fixed refCount leaks related to directory lookups and pioctl calls.
934 * Callbacks revoked during a race condition with an attempt to
935 obtain the same callback no longer result in an inaccessible
938 * New command line tool:
940 afsdacl : Set or reset the DACL to allow starting or stopping
941 the afsd service by any ordinary user.
943 Usage : afsdacl [-set | -reset] [-show]
945 -reset : Reset the DACL
946 -show : Show current DACL (SDSF)
948 * IP addresses are no longer queried once at startup. Instead IP
949 addresses are obtained as needed. Loopback adapter addresses are
950 no longer published to the server.
952 * Pay attention to the MIT KFW registry configuration for automatic
953 importation of MSLSA credentials. (SOFTWARE\MIT\Leash32,MsLsaImport)
955 * Fix (once again) case-sensitive comparisons which was apparently
958 * Activate support for vos listvol -format
960 * Population of the "AFS Client Admins" group failed on non-English
961 versions of Windows because the name of the "Administrators" group
962 is localized. Now we lookup the name of the group by using the
963 Administrators Group Alias Relative ID.
965 * Multiple cell token acquisition within afscreds.exe was broken in the
966 case of Kerberos 5 cross realm authentication. Instead of contacting
967 the KDC associated with the cell's realm, afscreds would obtain a
968 token from the KDC of the user's realm. This would result in
969 "invalid kvno errors" while authenticating to the AFS servers.
970 Unauthenticated access would work. The symptoms would vary based upon
971 whether or not the VLDB servers had been contacted using unauthenticated
972 connections prior to the user obtaining tokens.
974 * The list of ACL entries was becoming corrupted. It appears as if
975 an ACL when it expires was not being appropriately cleaned up. In
976 fact, it was left in the list of ACLs associated with the scache
979 * Changed the default @sys name list to "x86_win32 i386_w2k i386_nt40"
980 for 32-bit x86 systems. The default for itanium will be "ia64_win64"
981 and "amd64_win64" for amd 64-bit processors.
983 * When executing executables, Windows provides a mechanisms by which
984 the normal search for DLLs can be bypassed. If a file foo.exe is
985 being executed and there exists a file or directory "foo.exe.local"
986 (the contents are ignored if a file), then Windows will search for
987 DLLs first in the "foo.exe.local" directory and second in the
988 directory in which the "foo.exe" file is located.
990 Previous releases of OAFW would improperly return
991 STATUS_NOT_A_DIRECTORY instead of the expected
992 STATUS_OBJECT_PATH_NOT_FOUND. This would cause the Windows SMB client
993 to terminate the search for the DLL causing the execution of the
996 * Rework the reference counting of smb_vc_t objects. The references
997 stored in the waiting locks were not counted. This could result in
998 an assertion if the reference count drops to zero.
1000 * "fs wscell" returns "Freelance.Local.Root" for the workstation cell
1001 when running in freelance mode.
1003 * Added support for persistent caching of file contents, stat entries,
1004 volume data, cell data, and name lookup data. When the registry
1005 value, "NonPersistentCaching", is not defined or set to 0 the file
1006 specified by "CachePath" becomes a persistent cache file. The
1007 size of the cache file is computed at run time. It has a maximum
1008 size of approximately 1.2GB. The contents of the file will be
1009 validated according to the rules specified by the "ValidateCache"
1012 * Added support for UUIDs. UUIDs are kept for as long as the
1013 cache file is intact.
1015 * Added cmdebug.exe and support cache manager debugging callback
1016 interfaces in afsd_service.exe.
1018 Usage: cmdebug -servers <server machine> [-port <IP port>] [-long]
1019 [-addrs] [-cache] [-help]
1020 Where: -long print all info
1021 -addrs print only host interfaces
1022 -cache print only cache configuration
1024 * Symlinks to \\AFS\[all\]... will now be treated the same as
1025 symlinks to /afs/.... However, please use /afs/... as otherwise
1026 the symlinks won't work on Unix.
1028 * Correct a problem with local CellID allocation for cells whose
1029 server list is obtained via DNS instead of a CellServDB file. If
1030 the DNS information expires the CellID assigned to the entry will
1031 be changed. This causes all of the cm_scache_t objects which refer
1032 to the old cellID number to become useless. Attempts to access
1033 files or directories with cm_scache_t objects using the old cellID
1034 will fail since the server list cannot be obtained.
1036 * Correct deadlock condition in cm_EndCallbackGrantingCall which can
1037 be triggered if the volume referenced by the cm_scache_t object is
1040 * The AFS Service needs to respond to SERVICE_ACCEPT_SHUTDOWN messages
1041 in addition to SERVICE_ACCEPT_STOP.
1043 * Move RPC shutdown until after the SMB and RX shutdown procedures
1044 complete. Block until RPC shutdown is complete.
1046 * Modify afslogon.dll (integrated logon) to wait for service if its
1047 state is START_PENDING. If the timeout period occurs, reset to
1048 the retry interval and not the sleep interval.
1050 * When renewing the server list for a cell obtained via DNS AFSDB
1051 records, the cm_cell_t entry must be removed from the list of all
1052 cells. Otherwise, the list of cells will be corrupted.
1054 * In the dcache and scache modules, use the cm_scache_t dataVersion
1055 instead of the cm_fakeDirVersion.
1057 * Synchronize fs.c with the unix version.
1059 * The variable used to determine whether a file or virtual memory
1060 mapped cache is used was not properly initialized to a default
1061 value. If the registry setting "NonPersistentCaching" was not
1062 set, the choice would be random. Properly initialized to be
1065 * The memory mapped view was never unmapped before closing the file
1066 at service shutdown. This is now properly cleaned up.
1068 * Default location of Cache file is now %TEMP%\AFSCache
1072 * A bug affecting new installations of 1.3.75/76 would result in
1073 the creating of incorrect mountpoints in the freelance root.afs
1074 volume for the default cell.
1076 If "fs \\afs\all\<cellname>" lists a volume name of "root" instead
1077 of "root.cell", you have been affected by the bug. To correct the
1078 problem, execute the following commands:
1080 fs rmmount \\afs\all\<cellname>
1081 fs rmmount \\afs\all\.<cellname>
1083 fs mkmount \\afs\all\<cellname> root.cell <cellname>
1084 fs mkmount \\afs\all\.<cellname> root.cell <cellname> -rw
1088 * A bug has been fixed in the auto-generation of Freelance root.afs
1089 symlinks which produced random entries in the \\AFS\all directory.
1091 * Support has been added for multi-homed servers
1094 * Added a new registry value, "StoreAnsiFilenames", which can be used
1095 to force the use of ANSI character sets instead of OEM Code Pages.
1096 This feature is useful when users require the ability to create
1097 filenames with 8-bit characters and need to access the files from
1098 both Latin-1 based Unix systems as well as from Windows.
1100 Activation of this feature will prevent access to files stored with
1101 8-bit OEM characters.
1103 * Shutdown all SMB threads in a synchronized manner when stopping the
1106 * There is currently a maximum cache size of 1.3GB. The limit is imposed
1107 by the largest contiguous block of unused memory within the 2GB process
1108 space which can be assigned to the memory mapped file. Unfortunately,
1109 when the executable digital signature verification code is activated
1110 Windows sees fit to further segment the process memory which in turn
1111 reduces the size of the maximum cache file to less then 800MB. If
1112 larger cache sizes are desired, a new registry value should be set:
1114 HKLM\SOFTWARE\OpenAFS\Client (DWORD) "VerifyServiceSignature" = 0x0
1116 Setting this value will disable the runtime verification of digital
1117 signatures on afsd_service.exe and the afs dlls which it loads. It
1118 will not disable the the version number check on those same files.
1119 The signature verification is not a security messure and is only meant
1120 to enhance the ability to afsd_service.exe to detect potential
1121 destablizing mixtures of DLLs from incompatible distributions.
1123 Added code to auto-disable the signature verification check if
1124 the desired cache size is greater then 700MB.
1126 * Windows' WinTrustVerify(WIN_SPUB_ACTION_PUBLISHED_SOFTWARE) is
1127 used to verify the validity of the afsd_service.exe binary
1128 as well as each of the AFS DLLs loaded by the service. Not only
1129 must the digital signature be valid but the signatures of the
1130 DLL must be signed by the same entity as the service.
1132 * Implement new functions: cm_freelanceMountPointExists and
1133 cm_freelanceSymlinkExists. Use them along with other validity
1134 checks in cm_freelanceAddMount and cm_freelanceAddSymlink to
1135 ensure that name collisions do not occur and that empty strings
1136 are not valid file names.
1138 A symlink may not have a name which would resolve to a valid
1139 cell name. Doing so would prevent access to the cell.
1141 * Add missing cm_HoldSCacheNoLock call to Freelance mount point
1142 re-initialization code. The reference counts of the fake root.afs
1143 volume scache object(s) would become invalid when the mount point
1144 or symlink lists were altered.
1146 * Add registry entries to provide mappings from the afsdsbmt.ini
1147 to the new locations for applications which count on the use
1148 of the old Profile file APIs. These apps are likely to fail
1149 if the user does not have administrator privileges and the
1150 registry is locked down.
1152 * The afs_config.exe submounts dialog had two errors.
1153 First, attempts to remove entries failed because the registry
1154 key was being opened without KEY_WRITE privileges.
1155 Second, when editing a submount entry, changing the name
1156 would add a new key and leave the original one in place.
1157 Now the original submount will be removed if its name is
1160 * In recent months there have been several incidents in which
1161 users have experienced problems starting or accessing
1162 afsd_service.exe and after significant effort has been spent
1163 it has turned out that they have two versions of AFS on the
1164 machine or an inconsistent set of DLLs.
1166 Code has now been added to afsd_service.exe which will walk
1167 the list of modules loaded by afsd_service.exe and validate
1168 that the version of the AFS DLLs matches the version of the
1169 afsd_service.exe executable. If they do not match the service
1172 * When Freelance mode is enabled and there is no registry
1173 key HKLM\SOFTWARE\OpenAFS\Client\Freelance, afsd_service.exe
1174 will attempt to import the afs_freelance.ini file contents.
1175 If the file does not exist, it was creating a dummy file
1176 with a r/o and r/w entry for the default cell and then
1177 importing those values.
1179 This process has been changed. The temporary file is no
1180 longer created. Also, both the OpenAFS Client install
1181 directory as well as %WINDIR% are checked for previous
1182 afs_freelance.ini files.
1184 * Added support for VL_GetEntryByNameN(). Still need to add
1185 support for VL_GetEntryByNameU() for multi-homed support.
1187 * Fix a deadlock situation in afscreds.exe when canceling an
1188 auto-generated Obtain Tokens dialog
1191 * Fix the locking of objects during Directory Searches in the
1192 SMB/CIFS server. The failure to properly lock the reference
1193 counts was resulting in the premature freeing of smb_dirSearch_t
1194 objects while they were still in use by the SMB/CIFS client.
1195 This does not solve the "Invalid Handle" problem.
1197 * Fix Find Cell By Name pioctl call to return a valid cell
1198 name for the Freelance fake root.afs volume.
1199 "Freelance.Local.Root".
1201 * Fix the Explorer Shell Extension Symlinks->Add operation.
1202 The dialog template was missing and the link destination
1203 string was too short.
1205 * Add support for symlinks to Freelance root.afs volume
1206 Stored at HKLM\SOFTWARE\OpenAFS\Client\Freelance\Symlinks
1207 <number> = "<linkname>:<relative-path>."
1208 Use symlink.exe to create, list, or remove
1210 * Remove the fallback to the use of KFW's KRB4 library when obtaining
1211 tokens. We never obtain KRB4 tickets.
1213 * Fix AFS Client Configuration Control Panel to support new SysName
1216 * Fix a bug in afsd_service.exe which could result in the SysName
1217 not being read from the registry.
1220 * Add code to block the issuance of AFS tokens by aklog.exe or
1221 afscreds.exe when the Kerberos 5 principal name contains a dot.
1223 * Modify the IsAdmin() function to always treat the local SYSTEM
1224 account as an AFS client administrator. Affects fs.exe and
1227 * Modify the internal handling of Quota Exceeded errors
1229 * Upgrade all reference count fields in the Windows cache manager
1230 and the osi library to use unsigned long instead of signed short.
1231 A similar fix has been applied to the afs rpc (rx) library.
1233 * fix the Windows cache manager to prevent it from replacing the
1234 rx_connection object associated with the cm_conn_t object on each
1235 and every operation if "fs crypt" was set. This explains the
1236 dramatic performance difference when crypt is used vs clear.
1237 The problem: 'cryptall', a boolean flag indicating whether or not
1238 "fs crypt" is set, was being compared to the rx_connection
1239 cryptlevel which is either rxkad_clear:0 or rxkad_crypt:2.
1240 1 != 2 and therefore the rx_connection was always destroyed
1241 and replaced on each and every operation.
1243 Lock the cm_conn_t object around every call to RXAFS_xxxx functions.
1244 It is not safe for the cm_conn_t object to not be locked because
1245 rx_DestroyConnection might be called from another thread if:
1246 - the user's tokens have changed or expired
1247 - the crypt mode has changed
1249 This fix appears to have also taken care of the problems associated
1250 with Overlapped Writes resulting in Delayed Write errors.
1252 * fix NSIS installer's AdminGroup.exe to properly create and
1253 remove groups when given -create or -remove. The string comparison
1256 * fs sysname now accepts a list of sysname values
1258 * added a new registry value HKLM\SOFTWARE\OpenAFS\Client "IoctlDebug"
1259 DWORD which when set to a non-zero value will cause error message
1260 text to be output to stderr from the pioctl() routine. Useful in
1261 debugging failures of fs.exe, tokens.exe, etc.
1263 * added a test to the power management code to only perform a
1264 flush operation if there is at least one network adapter which
1265 is not a loopback adapter.
1267 * Fix bug in loading of registry value HKLM\SOFTWARE\OpenAFS\Client
1268 "EnableKFW". This value will not be read if the key
1269 HKCU\SOFTWARE\OpenAFS\Client exists; even if the "EnableKFW"
1270 value under that key does not.
1272 * provide mechanisms to force the use of krb524d for Kerberos 5
1273 ticket to AFS token conversion. For afslogon.dll and afscreds.exe
1274 there is a new registry value "Use524" and for aklog.exe a new
1275 command line parameter "-m".
1277 * Fix the pattern matching algorithm to properly match patterns
1280 * smb_ReceiveCoreRename() was factored to produce smb_Rename()
1281 which is used by both the original function and the new
1282 smb_ReceiveNTRename(). smb_ReceiveNTRename() supports the
1283 creation of HardLinks in addition to Renaming. smb_Link()
1284 is a new function which creates HardLinks via cm_Link().
1285 cm_Link() is a new vnodeops function which creates links
1288 smb_ReceiveNTRename() does not support the File Copy and
1289 Move Cluster Information operations described in its interface.
1290 ReceiveNTRename is under documented in CIFS-TR-1p00_FINAL.pdf.
1292 * When opening files via symlinks, we should follow the symlinks
1293 until we reach the actual file stat cache entry. The stat cache
1294 entry of the file should then be stored in the FID instead of
1295 stat scache entry of the symlink.
1297 * return bad operation errors for all unimplemented functions
1298 even if we do not know the functions exist.
1300 * Log bad packets and unknown operation packets to the trace log
1302 * Map CM_ERROR_BADOP to STATUS_NOT_SUPPORTED instead of
1305 * Update list of known CIFS operations to include all those listed
1306 in CIFS-TR-1p00_FINAL.pdf.
1308 * Modify the handling of HKLM\SOFTWARE\OpenAFS\Client\Submounts
1309 to support the REG_EXPAND_SZ type.
1312 * A new Windows authorization group "AFS Client Admins" is now
1313 created and populated with the members of the "Administrators"
1314 group. The group is used to determine which accounts on the
1315 machine may be used to modify the AFS Client Configuration via
1316 the UI and command line tools. afs_config.exe, fs.exe,
1318 * Modify the WinLogon Logoff Event Handler to query NT4 domain
1319 controllers for the remote profile path if Active Directory
1320 services are not available.
1322 * Fix aklog.exe to not add the AFS ID to the username
1324 * PTS registration of new users to foreign cells has been added to
1327 * The cm_Daemon thread is used to perform checks for
1328 down servers, up servers, volumes, callback expirations,
1329 lock maintenance and token expiration. Due to a gaff in
1330 larger integer division the thread never performed any
1331 work. Instead the current time computation would always
1332 be less then the trigger times. This had an adverse affect
1333 on the client's ability to maintain communication with servers,
1334 keep volumes up to date, and flush user tokens and acls
1335 when they have expired. This was broken when the 1.3 branch
1336 was modified to support VC7 which no longer included
1339 * An initialization problem with the Freelance code was
1340 detected while fixing the callbackRequest. The cm_rootSCachep
1341 object is obtained during afsd_InitDaemons() but the callback
1342 information is incomplete. The callback information will not
1343 be obtained until cm_MergeStatus is called from within
1344 cm_GetCallback. Unfortunately, cm_SyncOp did not properly
1345 test for the conditions under which the callback information
1348 * Reports have been filed indicating that callbacks were
1349 being lost. An examination of the code indicated that the
1350 cm_server_t objects were not being properly reference
1351 counted by the cm_scache_t and cm_callbackRequest_t objects.
1352 In particular, the cm_server_t objects may have been freed
1353 from beneath the cm_conn_t objects.
1355 All of the reference counting is now done via the functions:
1360 this improves the ability to track the referrals.
1362 Each cm_BeginCallbackGranting Call now allocates a reference
1363 to the cm_server_t. The cm_EndCallbackGrantingCall either
1364 frees the reference or transfers it to the cm_scache_t
1365 cbServerp field. These are then appropriately tracked
1366 through the cm_Analyze call.
1368 * Ensure that the dnlc hash table is the same size as the
1369 dir name hash table (as per original author's note).
1370 Increase the dnlc CM_AFSNCNAMESIZE to a multiple of 8
1371 for compatibility with 64-bit systems.
1373 * fix smb_ApplyV3DirListPatches to properly apply the hidden
1374 attribute to dotfiles when the infoLevel < 0x101 and
1375 cm_SyncOp has failed.
1377 * Fix the Freelance registry initialization code. There
1378 was a possibility that some systems could end up with
1379 garbage in the registry during a clean install.
1382 * file and directory names beginning with "." will now be given the
1383 hidden attribute when the volume access is anonymous. this matches
1384 the behavior when the volume access is via an authenticated user.
1386 * Added a change monitor to the HKLM\SOFTWARE\OpenAFS\Client\Freelance
1387 key. When a change occurs mark the root.afs data as invalid and
1388 for it to be reloaded on the next access. This allows administrators
1389 to modify the mount point list without restarting the service.
1391 The freelance client used to provide a fake modification time for
1392 the root.afs volume data and its mount points of 7/09/2001 14:24 EDT.
1393 Added code to extract the last modification time of the Freelance
1394 registry key and use that instead. The time now represents the
1395 most recent mount point change.
1397 * PTS registration of new users to foreign cells has been added to
1400 * Additional Cache Control and Credential Manager options have been
1401 added to the WiX installer. See deployment guide for details.
1403 * The CachePath setting is now optionally a REG_EXPAND_SZ type
1405 * The WiX installer has been upgraded. Version 2.0.1927.1 is now
1408 * The loopback installation code may have had a problem updating the
1409 %ETC%\HOSTS file which could have resulted in a premature failure.
1410 Work around code has been added for the case where the file cannot
1413 * The default max chunksize was increased from 15 (32K) to 17 (128K)
1414 because Windows sends 64K blocks when using overlapped writes.
1416 * The default number of server threads was increased from 4 to 25 to
1417 better handle overlapped writes.
1419 * The "AfscredsShortcutParams" registry value was not being properly
1420 loaded by afscreds.exe. Therefore, the default value was always being
1421 used instead of the value set by the installer.
1423 * Windows XP provides downgrade attack detection to prevent an attacker
1424 from being able to force the use of NTLM simply by disrupting
1425 communication with the KDC. This attack cannot exist between the
1426 Windows CIFS client and the AFS Client Service. Therefore, when a
1427 downgrade has been detected the afs pioctl library will force the
1428 establishment of a new CIFS connection using NTLM.
1430 * A locking error was discovered surrounding all references to volume
1431 server lists within the cm_cell.c source file.
1433 * The logged into Windows username was incorrect on Terminal Server
1436 * A new registry value "NonPersistentCaching" was added to the service
1437 parameters key. When set to a non-zero value, the afs cache is stored
1438 in the Windows paging file. There are two limitations to choosing
1440 1. when persistent caching is implemented it won't work with
1441 this flag set since there will be nothing to persist.
1442 2. with this flag set the initial paging allocation cannot be
1443 changed while the service is running
1445 * An initialization bug was discovered in aklog.exe which affected users
1446 who have a domain name for their afs servers which could not be mapped
1450 * afs_config.exe now validates cell names against DNS in addition
1451 to the CellServDB file.
1453 * In order to allow the freelance client to connect to a volume with ID
1454 equal to 1 on the default cell we changed the fake root.afs volume ID
1455 once again. This time we choose 0xFFFFFFFF. In addition, we change
1456 the cell ID of the fake root.afs volume from 1 to 0xFFFFFFFF as well.
1457 It will now be impossible for a volume ID to match that of another
1458 cell unless the client is connected to 0xFFFFFFFD cells. That should
1459 be enough room for growth.
1461 * Fix "fs mkmount" command to work with UNC paths and when
1462 started from non-AFS drives. It is now possible to create a mount
1463 point in the freelance fake root.afs volume with the command
1465 fs mkmount \\AFS\all\<directory-name> <volume-name> <cellname>
1469 fs mkmount \\AFS\all\openafs.org root.cell openafs.org
1470 fs mkmount \\AFS\all\.openafs.org root.cell openafs.org -rw
1472 * The algorithm used to re-attempt access to the servers associated with
1473 a volume has been altered to properly address the case in which all
1474 servers have been marked down. The previous algorithm did not reset
1475 the server's down flags so the servers were never actually retried.
1476 This caused a problem with active volumes if the network connectivity
1477 was lost as could be the case with a network cable removal, wireless
1478 drop, or laptop hibernation. With the fix volume access is restored
1479 almost instantenously when network connectivity becomes available.
1481 * Support for SMB/CIFS browsing has been added to the AFS Client Service
1482 SMB server. It is now possible to use "NET VIEW \\AFS" to obtain a
1483 listing of AFS submounts and freelance mount points. Support for
1484 NETSHAREENUM, NETSHAREGETINFO, NETSERVERENUM2, NETSERVERGETINFO
1485 significantly enhances the behavior of AFS volumes within the Explorer
1486 Shell. For instance, "AFS" now shows up as server in the Explorer
1487 with each submount or freelance mount point visible as a share.
1488 The right click menu in each folder now works with full functionality
1489 on a consistent basis.
1491 * The network provider can be configured to have different behavior
1492 depending on the domain that the user logs into. These settings are
1493 only relevant when using integrated login. A domain refers to an
1494 Active Directory (AD) domain, a trusted Kerberos (non-AD) realm or the
1495 local machine (i.e. local account logins). The domain name that is
1496 used for selecting the domain would be the domain that is passed into
1497 the NPLogonNotify function of the network provider. (see registry.txt
1500 * Added a new registry value [HKCU\SOFTWARE\OpenAFS\Client]
1501 "Authentication Cell" which may be used to specify a default
1502 authentication cell for afscreds.exe which is different from
1503 the default cell for the AFS Client Service daemon.
1505 * Added a Logoff WinLogon Event Notification function to afslogon.dll.
1506 afslogon.dll moved to %WINDIR%\System32\.
1507 New registry entries added to register the dll for Winlogon events.
1509 The logoff event will now force a call to ktc_ForgetAllTokens()
1510 using the context of the user being logged off as long as the
1511 user's profile is not loaded from within AFS. If the profile
1512 was loaded from AFS we can't release the tokens since the Logoff
1513 event is triggered prior to the profile being written back to
1514 the its source location. This is now performed in an XP SP2
1517 * Windows XP SP2 Internet Connection Firewall interoperability
1520 * The %WINDIR%\afsdsbmt.ini contains four sections:
1521 Submounts, Drive Mappings, Active Maps and CSC Policies.
1522 The Submounts and CSC policies are now stored in the registry under
1523 [HKLM\SOFTWARE\OpenAFS\Client\Submounts]
1524 [HKLM\SOFTWARE\OpenAFS\Client\CSCPolicy]
1525 The Drive Mappings and Active Maps are stored in the registry under
1526 [HKCU\SOFTWARE\OpenAFS\Client\Mappings]
1527 [HKCU\SOFTWARE\OpenAFS\Client\Active Maps]
1529 There is no automatic migration of this data as it would be impossible
1530 to consistently migrate data to user profiles which may not be active
1531 when the machine is updated.
1533 * The %WINDIR%\afs_freelance.ini contains lists of mountpoints for the
1534 fake root.afs volume. For the same reasons as for the cellservdb file,
1535 this information should not be in %WINDIR%. This information is now
1536 kept under the registry key
1537 [HKLM\SOFTWARE\OpenAFS\Client\Freelance]
1539 The data from the afs_freelance.ini file will be automatically
1540 migrated to the registry on first execution of afsd_service.exe
1542 * Keeping the CellServDB file in the location %WINDIR%\afsdcell.ini is
1543 troublesome for several reasons. One, it is confusing for those who
1544 expect the file to be named "CellServDB" instead of "afsdcell.ini".
1545 Two, this file is not a Windows Profile formatted file. Three,
1546 applications should not be reading or writing to %WINDIR%. It causes
1547 problems for Windows Terminal Server.
1549 The new location of CellServDB will be the OpenAFS Client install
1550 directory which is by default C:\Program Files\OpenAFS\Client and can
1551 be determined by querying the registry for
1552 [HKLM\SOFTWARE\TransarcCorporation\AFS Client\CurrentVersion]PathName
1554 The existing afsdcell.ini will be migrated by the NSIS installer.
1555 The Wix installer must still be updated to do the same.
1557 * Change NSIS installer to use DNS by default; to remove Integrated Logon
1558 High Security mode; and to add Terminal Services compatibility registry
1559 entries to allow the OpenAFS tools to find the afsdcell.ini and other
1560 configuration files in %WINDIR%.
1562 * Add support for authenticated SMB connections. This will remove
1563 the need for high security mode in most situations. Both NTLM
1564 and Extended Security (GSS SPNEGO) modes are supported. Effectively,
1565 only NTLM can be used even though Kerberos is now supported. The
1566 reason is that it is not possible to construct a service principal
1567 which is unique to each individual machine.
1569 SMB Extended Auth does not work on XP SP2 unless one of two registry
1570 modifications are made:
1572 (1) To disable the check for matching host names on loopback connections
1573 set this key. This does not require a reboot:
1575 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
1576 "DisableLoopbackCheck"=dword:00000001
1578 (2) To add the AFS SMB/CIFS service name to an approved list. This
1579 does require a reboot:
1581 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
1582 "BackConnectionHostNames"=multi-sz "AFS" "MACHINE-AFS"
1584 afsd_service.exe will automatically add the current Netbios Name
1585 to the BackConnectionHostNames list and then temporarily disable
1586 the loopback check for one cycle of startup/shutdown of the service.
1587 We assume most folks do not start/stop without a reboot so this
1588 will be adequate in most cases.
1590 * Fix security hole in afslogon.dll which allowed passwords to be
1591 sent in clear text to the KDC in a misformed principal name.
1593 * Fix cm_GetCell() to properly handle expired dns entries
1596 * If Freelance mode is active and the afs_freelance.ini
1597 file does not exist, do not create an empty file.
1598 Instead create a file containing ro and rw mountpoints
1599 to the default cell using the standard conventions.
1601 * Modify the Freelance support to handle the ability
1602 to create rw mount points in the fake root.afs volume.
1604 * Changed the RPC mechanism used for token setting from
1605 named pipes to local. Use of named pipes can be restored
1606 by setting the environment variable AFS_RPC_PROTSEQ to
1609 Named pipes were required when a Windows 9x system was
1610 using a NT system in gateway mode which is incompatible
1611 with our use of local loopback adapters.
1613 * In afscreds.exe, if a username of the form user@REALM is
1614 specified and no password is specified, do not perform a
1615 kinit operation. Only perform the aklog functionality.
1617 * Add a new registry value which allows the number of processors
1618 on which afsd_service.exe executes to be restricted. Valid
1619 values are 1..numOfProcessors
1621 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAfsDaemon\Parameters
1625 * A second MSI based installer option is now available.
1627 * Fixed Kerberos 5 kinit functionality in afscreds.exe to properly
1628 request tickets for user/instance@REALM instead of just user@REALM
1630 * Modify the Power Management Notify routine to wait for the Hard Dead
1631 timeout period instead of a fixed 19 seconds. With the longer timeout
1632 periods Hibernation and Standby could never succeed when network
1633 connectivity is not available.
1635 * The following fs.exe commands are now restricted to Administrator:
1636 - checkservers with a non-zero timer value
1639 - sysname with a new sysname list
1648 setting the default sysname for a machine should be done via the
1649 registry and not via "fs sysname".
1651 * NSIS installer adds options to install Debugging Symbols
1652 and the Microsoft Loopback Adapter; the user is now also
1653 given the ability to select the afscreds.exe startup options.
1655 * Build system modified to generate symbols for FREE (aka RELEASE)
1656 builds as well as CHECKED (aka DEBUG) builds
1658 * Sites which have a volume ID of 0x20000001 assigned to their
1659 root.cell volumes have been experiencing problems with accessing
1660 the root.cell volume of their cell when Freelance mode has been
1661 active. This was because 0x20000001 was assigned to the fake
1662 root.afs volume created by freelance. The fake volume id is
1663 now set to 0x00000001 to prevent conflicts.
1665 * The timeout logic in the AFS Client Service has been wrong
1666 for sometime. It is based on two different assumptions.
1667 First, the SMB client timeout is a fix value as was the case
1668 with OS/2 Lan Manager. This assumption is incorrect. The
1669 SMB timeout in Windows is a dynamic value computed based upon
1670 a fixed minimum timeout to which is added time based upon the
1671 size of the request and the performance characteristics of
1672 the connection. Second, it is the responsibility of the
1673 SMB Server to enforce the timeout requirements of the client.
1674 This is untrue. The SMB Server cannot be expected to know
1675 the requirements of the client. More importantly, if the
1676 SMB server uses the SMB client timeout as a value to restrict
1677 its behavior as an RX client, the performance characteristics
1678 of the local SMB session would be used to prematurely terminate
1679 WAN connections with significantly different performance
1682 The timeout logic has therefore been modified in the following
1684 . the Lan Manager Workstation (SMB) Session Timeout is used only
1685 as a basis for configuring the Connection Dead Timeout
1686 and Hard Dead Timeout values. The Connection Dead Timeout
1687 must be at least 15 seconds longer than the SMB Timeout
1688 and the Hard Dead Timeout must be at least double the
1689 Connection Dead Timeout.
1690 . New registry entries have been added to allow the Connection
1691 Dead Timeout and Hard Dead Timeout values independent of the
1692 Lan Manager Workstation Session Timeout
1693 . The test to enforce the SMB Client Timeout has been removed.
1695 One of the side-effects of removing the enforcement of the SMB
1696 Client Timeout is that regardless of whether or not the SMB client
1697 is available to receive the response (and how would the SMB server
1698 know) the RX protocol response can be used to update the AFS
1699 Client Service state for ready access by future SMB client
1702 This should be the end of the "Server paused or restarting messages"
1704 * Add support for arbitrary UNC paths to the pioctl() support.
1705 This enables the fs commands as well as the AFS Shell Extension
1706 to work correctly when UNC paths are being used.
1708 * Fix afscreds.exe (by updating afskfw.lib) to search for cells via
1709 DNS if the cell configuration cannot be determined via CellServDB
1711 * Add debug info to test whether CM_BUF_WAITING or CM_SCACHE_WAITING
1712 are ever set more than once at a time
1714 * Fix the management of lists of cm_cell_t structures when using
1715 DNS to lookup cell information. The previous code would fail to
1716 reuse the same cellID for a cell if DNS was used more than once
1717 for a given cell name. When the ttl expired, a single cm_cell_t
1718 could be inserted into the cm_allCellsp list more than once
1719 producing a loop. In addition, the vlServerp list belonging to
1720 the cell was not freed resulting in improper refCounting of the
1723 * Add DNS support to cm_IoctlNewCell() which previous only examined
1726 * Add cm_FreeServer() function and call it from cm_FreeServerList()
1727 to properly garbage collect cm_server_t objects
1729 * Add numVCs variable to smb.c to track the number of smb_vc_t
1730 objects created and use it to initialize the vcID field which
1731 previously was set to 0 in all objects resulting in FindByID
1734 * Fixed DNS lookups to work consistently throughout the OpenAFS
1735 product instead of just from within the afsd_service.exe
1737 * Added a runtime check to ensure that AFS Client Service SMB
1738 Server is accepting connections before attempting to mount
1741 * Read IP addresses for volume servers out of the CellServDB
1742 file if gethostbyname() on the hostname fails.
1744 * Fix getcellconfig() to populate both the Hostnames as well
1745 as IP addresses when loading cell data via DNS
1747 * Increase the Connection Dead Time to 50 from 20 seconds
1748 Increase the Hard Dead Time to 120 from 40 seconds
1749 (matches the Unix values)
1751 * Fixed an assertion validating the number of allocated NCBs
1753 * Fixed the build environment to consistently build for
1754 Windows 2000 and above. (APPVER = 5.0)
1756 * Fixed rx_debug to properly validate the receipt in incoming
1757 data with select() and recvfrom(). Do not copy data out of
1758 the socket buffer unless success is indicated.
1761 * afsd_service.exe will now display a message box to the
1762 desktop when it terminates due to an IP Address Change.
1764 * installer no longer deletes AFS Server configuration data
1767 * installer generates a warning dialog if the RPC service
1768 is not properly configured
1770 * installer compressed with lzma instead of bzip2
1772 * afsd_service.exe shutdown crash solved once and for all
1774 * reference counting of smb_vc_t data structures improved
1776 * name space collision of smb_fid_t event objects corrected
1778 * the output of "fs memdump" is now written to
1779 %WINDIR%\TEMP\afsd_alloc.log
1781 * the file TaAfsApp_1033.dll is now properly installed allowing
1782 the User Manager to start
1784 * a new algorithm is used for computing filename pattern matches
1786 * afscreds.exe now accepts user names containing instance
1789 * Fix the Directory Name Lookup Cache to be case-sensitive.
1790 This is crucial in environments in which a Windows client
1791 is accessing a directory with more than one filename that
1792 differs only by case. If the directory contains "FOO"
1793 and "Foo". You want "DEL Foo" to delete the correct one.
1794 We still have a problem in that "DEL foo" will delete a
1795 random filename. This will be addressed in a future release.
1797 * Fix afscreds.exe -M option (renewMaps) to work when High
1798 Security mode is off. Also, remember to disable the ActiveMap
1799 flag in afsdsbmt.ini when a drive mapping is removed.
1801 * Updates to NSIS installer script. AFS Server configuration
1802 data will not be destroyed on un-install or re-install.
1803 Use a better compression algorithm.
1805 * afslogon.dll now uses KFW to obtain tokens when available
1807 * afslogon.dll when given an all uppercase username will
1808 attempt to authenticate with both the uppercase name
1809 and an all lowercase variation
1811 * DST modification removed. The fix appears to make things
1812 worse after a reboot of the machine.
1814 * fs.exe: added "cscpolicy" which is used to
1815 change client side caching policy for AFS shares
1817 Usage: fs cscpolicy [-share <AFS share>] [-manual] [-programs]
1818 [-documents] [-disable] [-help]
1820 * Several uninitialized variables have been initialized
1822 * It is now possible to obtain tokens using cross realm
1823 Kerberos within afscreds.exe:
1825 user: jaltman@ATHENA.MIT.EDU
1827 Will obtain a cross realm ticket for jaltman/DEMENTIA.ORG@ATHENA.MIT.EDU
1828 will will in turn be used to obtain afs@DEMENTIA.ORG.
1829 The resulting token will be stored with the display name
1830 jaltman@ATHENA.MIT.EDU@dementia.org
1832 * aklog.exe has been added to the client
1834 Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
1835 [[-p | -path] pathname]
1839 -d gives debugging information.
1840 krb_realm is the kerberos realm of a cell.
1841 pathname is the name of a directory to which you wish to authenticate.
1842 -noprdb means don't try to determine AFS ID.
1843 -5 or -4 selects whether to use Kerberos V or Kerberos IV.
1844 (default is Kerberos V)
1845 No commandline arguments means authenticate to the local cell.
1848 * All of the resource files have been restructured to adhere to
1849 a set of rules IBM implemented for loading string resources.
1850 These rules had either been forgotten or were not discovered
1851 by folks working on the OpenAFS sources. The end result was
1852 memory corruption. This is primary item which was preventing
1853 the AFS Server from working.
1855 * Increased the size of the maximum ticket size stored in a token
1856 from 344 bytes to 12,000. Increased the buffers used to convey
1857 messages between the pioctl() caller and the SMB Server from
1858 1000 bytes to 12,512. The code appeared to have been writing
1859 above the top of the stack by quite a few number of bytes.
1860 (The increased ticket size is necessary for the next item.)
1862 * When obtaining AFS Tokens via KFW, krb524 is no longer required.
1863 Instead the raw Kerberos 5 ticket is used in its entirety. This
1864 is extremely important as it allows us to use pure Kerberos 5 KDCs
1865 as the source of the AFS authentication. The use of up to 12,000 byte
1866 tickets will allow tickets produced by all versions of Microsoft
1867 Active Directory to be used.
1868 - create a user account.
1869 - designate it DES only
1871 - specify its UPN to be "afs@realm"
1872 - assign a SPN of "afs/cellname" to the UPN with setspn.exe
1874 * Do not enforce the funky 8dot3 pattern matching rule that the first "."
1875 is special when using long file names. (you must use "*.*" and not "*")
1876 Instead only enforce it when performing 8dot3 searches.
1878 * Fixed the DST problem with creation times being set one hour ahead
1880 * Fixed the problem when using \\afs\cell-alias. For example,
1881 \\afs\uncc instead of \\afs\uncc.edu. Do not a new cell struct
1882 for the alias name; instead simply expand the name. One of the
1883 symptoms of this problem was a loss of acquired tokens.
1885 * Fixed the AFS Shell Extension. The Symbolic Link menu was empty
1886 of strings. (Only English strings provided.)
1888 * Fixed the installer to properly replace in use files.
1890 * Fixed the build system to cleanup generated component version files
1892 * The release build compiled with MSVC 6.0 compiler to avoid the
1893 afsd_service.exe shutdown crash. This does not solve the problem
1894 but simply avoids it for the time being.
1898 * fix afslogon.dll to not corrupt memory when High Security mode
1901 * fix afsd_service.exe to not attempt to restore the stack when
1902 an exception occurs. (not safe in multi-threaded programs)
1904 * fix uninstaller to properly remove the CRT and MFC DLLs
1906 * remove a Message Box from afscreds.exe when getcellconfig()
1907 fails on a kerberos realm which is not a cell
1909 The following is a list of changes to the OpenAFS for Window client
1912 * "fs setserverprefs" will leave afsd service deadlocked
1914 * "vos listaddrs" will core dump
1916 * installer sets the appropriate keys to support Integrated Logon
1918 * installer disables the "Find Lana by Name" functionality as it
1919 was causing headaches for many users
1921 * fix the intermittent crash of the power management thread when
1922 shutting down the AFS Client Service
1924 * optimizes the obtain drive mount list functionality which is
1925 executed every time the mount tab in afscreds.exe and afs_config.exe
1926 are refreshed. (this happens a lot)
1928 * fix the service shutdown logic. add the STOP_PENDING state
1929 and do not accept additional service events after we declare
1932 The following is a list of changes to the OpenAFS for Window client
1935 * flexelint was run against the source tree and hundreds (perhaps
1936 thousands) of corrections were applied to ensure prototypes
1937 were in use; types were used consistently; variables were
1938 initialized; unused variables were removed; etc.
1940 * A wide variety of instrumentation was added including the
1941 ability to produce a stack trace from within afsd_service.exe
1944 * Dynamic configuration of the RDRtimeout value based upon the
1945 LanMan Workstation Session Timeout
1947 * The mount root no longer needs to be called "/afs". This
1948 is now set by a registry value "MountRoot" within the key
1949 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
1951 * The cell list is now only read out of afsdcell.ini when the
1952 file changes instead of each time a cell is resolved.
1954 * Thread synchronization was added to cm_server.c and ktc_nt.c
1956 * All calls to GlobalAlloc()/GlobalFree() were replaced with
1957 calloc()/free(). The Global functions were needed on Windows 3.x
1958 but have caused a variety of problems on the Win32 platforms.
1959 Avoiding them is highly recommended by several Microsoft
1960 Knowledgebase articles
1962 * Support for Symbolic Links added to the AFS Shell Extension
1964 * Added a registry value "OverlayEnabled" to determine if
1965 Shell Extension Overlays should be enabled.
1966 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters
1968 * New Build system to support VC6, VC.NET, VC.NET2003 compilers and
1969 separate trees for checked and free builds. Build system supports
1970 a custom directory src\WINNT\extra which can be used as a grafting
1971 location of organization specific additions to the build tree.
1973 * New installer built using NSIS 2.0.
1975 * Named all kernel objects in order to allow them to be monitored
1976 with tools such as SysInternals' ProcExp.exe.
1978 * Introduced new EventLog framework for AFSD
1980 * Introduced Power Management interface to AFSD for Standby and
1981 Hibernate modes to allow cache to be flushed prior to network
1984 * Utilize Win32 DNSQuery API instead of internal routines. This
1985 allows DNS SRV queries to be sent to all current domain name
1986 servers. Not just one specified in an INI file. DNS is now
1989 * "NetbiosName" registry value may be used to specify a fixed
1990 Netbios Name such as "AFS" to be used instead of "HOSTNAME-AFS"
1991 when the loopback adapter is in use. If you need to use the
1992 old notation with a loopback adapter installed specify a registry
1995 "NetbiosName" REG_EXPAND_SZ = "%COMPUTERNAME%-AFS"
1997 * Refactor all modules which depend on LAN Adapter and NetbiosName
1998 determination in a new library: lanahelper.lib. This allows for
1999 consistent behavior throughout the product.
2001 * Move the afsd.log and afsd_init.log files to the directory specified
2002 by the "TEMP" environment variable. This is usually %WINDIR%\TEMP
2003 for services. Added the Date to the log entries.
2005 * New registry value "RxMaxMTU" used to limit the size of the RX
2006 packets sent by the AFS Client Service to the Server. In order
2007 to enable OpenAFS to work across the Cisco IPSec VPN the packet
2008 size must be restricted to 1264 or smaller. The latest NSIS
2009 installer sets a value of 1260 by default.
2011 * New registry value "RxNoJumbo" to disable the use of Jumbo Rx
2012 packets. This is not needed in order to work across the Cisco
2013 VPN but might be needed for other network environments. This
2014 value is not set by the NSIS installer.
2016 * New registry value "HideDotFiles" is used to apply the Hidden
2017 attribute to files whose names begin with a '.'. This value
2018 is set by the NSIS installer.
2020 * New registry value "MaxMpxRequests" allows the maximum number
2021 of multiplexed sessions to be configured at run time. This
2022 value is not set by the NSIS installer. The default value is
2025 * New registry value "MaxVCPerServer" allows the maxmimum number
2026 of VCs per server to be configured at run time. This value is
2027 not set by the NSIS installer. The default value is 100.
2029 * New registry value "AllSubmount" allows the "all" submount to
2030 be disabled by setting its value to 0x00.
2032 * Allow cells names to be valid mount points
2033 \\<netbiosName>\<cellname>
2035 * Store the active state of drive mappings in order for afscreds.exe
2036 to restore them upon startup
2038 * Add exception handling to generate a Stack Trace to the afsd_init.log
2039 file if one happens to occur.
2041 * Add lots of logging to help detect the cause of invalid SMB packets
2043 * Enable Kerberos for Windows to be used to obtain AFS Tokens via
2044 conversion of Kerberos 5 "afs" service tickets. Supports auto-
2045 renewal of expiring tokens as long as afscreds.exe is running.
2047 * New afscreds.exe command line options:
2049 -M = renew drive maps
2050 -N = ip address change detection
2053 * New registry value "EnableKFW" in {HKCU,HKLM}SOFTWARE\OpenAFS\Client
2054 determines whether or not MIT Kerberos for Windows should be used
2055 to obtain tokens via Kerberos 5 tickets.
2057 * New registry value "AfscredsShortcutParams" in
2058 {HKCU,HKLM}SOFTWARE\OpenAFS\Client
2059 determines the command line parameters to be specified when "fixing"
2060 the AFS Shortcut in the user's startup folder.
2062 * The "ShowTrayIcon" registry value has been moved from
2063 HKLM\Software\TransarcCorporation\AFS Client\AfsCreds to
2064 {HKCU,HKLM}SOFTWARE\OpenAFS\Client
2066 * The <cell name> registry values used to store the token expiration
2067 reminders have been moved from
2068 HKLM\Software\TransarcCorporation\AFS Client\AfsCreds to
2069 {HKCU,HKLM}SOFTWARE\OpenAFS\Client\Reminders
2071 * Obtain the Logon User Name from the Explorer key when available
2073 * new text document doc\txt\winnotes\registry.txt lists all registry
2074 values used by OpenAFS (excluding the AFS Server)
2076 * BUG: rx_securityClass objects were not properly reference
2077 counted and were never freed.
2079 * BUG: reduce the number of conditions under which CM_ERROR_TIMEOUT
2080 would be generated. The existence of a server does not imply
2081 that it is not down. If all of the servers for a cell are down
2082 return CM_ERROR_NOSUCHVOLUME instead. This prevents the Explorer
2085 * BUG: the directory name lookup cache failed to free the entries
2086 in the cache when the name cache entries cycled. The entries
2087 in the cache would become dereferenced without being freed.
2089 * BUG: fs setserverprefs could be executed without Administrator
2092 * BUG: the number of allocated NCB objects (100) exceeded the number
2093 which could actually be waited upon by the kernel (64). Any objects
2094 which were utilized above the limit could never have event completions
2097 * BUG: smb_username_t objects were not being reference counted and
2098 were not properly freed.
2100 * BUG: smb_tid_t objects could under unusual circumstances be freed
2101 before they were no longer referenced.
2103 * BUG: smb_fid_t object pointer were frequently used even when
2104 their value could be NULL. They were not properly released and
2105 therefore they were never freed.
2107 * BUG: smb_packet_t data structures were not completely initialized
2110 * BUG: when Rx produces a CM_ERROR_NOIPC error do not return "Access
2111 Denied" because that causes the Explorer Shell to try again until
2112 access is obtained. Instead return "Remote Resources" which allows
2113 the shell to move on and treat the error as transient.
2115 * BUG: when initializing the NCBreturns structure, separate Event objects
2116 were created for each NCB although a single Event object was supposed
2117 to be shared by all.
2119 * BUG: smb_dirSearch_t objects were not being properly referenced counted
2122 * BUG: smb_tran2Packet_t objects were not being properly referenced
2125 * BUG: directory path creation did not handle the case of multiple
2126 directories requiring creation in one attempt
2128 * BUG: SMB requests which required an Extended Response were ignored.
2129 This prevented some files from being written to AFS volumes.
2131 * BUG: character strings were being freed even after they were
2132 inserted into in use data structures
2134 * BUG: inconsistent usernames were used when High Security mode was
2135 enabled. (there is still much to do in this area)
2137 * BUG: pioctl() calls which require out of band RPC operations were
2138 susceptible to race conditions when performed by multiple processes
2140 * BUG: memory allocation and deallocation crossed instances of the
2141 C Runtime Library producing memory leakage and corruption in
2142 afscreds and the client configurator.
git://git.openafs.org / openafs.git / blob