Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.1 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.3 *** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.1 Tue Aug 10 00:10:44 2004 --- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt Mon Aug 23 11:54:34 2004 *************** *** 1,3 **** --- 1,73 ---- + Since 1.3.70: + * A new Windows authorization group "AFS Client Admins" is now + created and populated with the members of the "Administrators" + group. The group is used to determine which accounts on the + machine may be used to modify the AFS Client Configuration via + the UI and command line tools. afs_config.exe, fs.exe, + + * Modify the WinLogon Logoff Event Handler to query NT4 domain + controllers for the remote profile path if Active Directory + services are not available. + + * Fix aklog.exe to not add the AFS ID to the username + + * PTS registration of new users to foreign cells has been added to + afscreds.exe + + * The cm_Daemon thread is used to perform checks for + down servers, up servers, volumes, callback expirations, + lock maintenance and token expiration. Due to a gaff in + larger integer division the thread never performed any + work. Instead the current time computation would always + be less then the trigger times. This had an adverse affect + on the client's ability to maintain communication with servers, + keep volumes up to date, and flush user tokens and acls + when they have expired. This was broken when the 1.3 branch + was modified to support VC7 which no longer included + largeint.lib + + * An initialization problem with the Freelance code was + detected while fixing the callbackRequest. The cm_rootSCachep + object is obtained during afsd_InitDaemons() but the callback + information is incomplete. The callback information will not + be obtained until cm_MergeStatus is called from within + cm_GetCallback. Unfortunately, cm_SyncOp did not properly + test for the conditions under which the callback information + must be obtained. + + * Reports have been filed indicating that callbacks were + being lost. An examination of the code indicated that the + cm_server_t objects were not being properly reference + counted by the cm_scache_t and cm_callbackRequest_t objects. + In particular, the cm_server_t objects may have been freed + from beneath the cm_conn_t objects. + + All of the reference counting is now done via the functions: + cm_GetServer + cm_GetServerNoLock + cm_PutServer + cm_PutServerNoLock + this improves the ability to track the referrals. + + Each cm_BeginCallbackGranting Call now allocates a reference + to the cm_server_t. The cm_EndCallbackGrantingCall either + frees the reference or transfers it to the cm_scache_t + cbServerp field. These are then appropriately tracked + through the cm_Analyze call. + + * Ensure that the dnlc hash table is the same size as the + dir name hash table (as per original author's note). + Increase the dnlc CM_AFSNCNAMESIZE to a multiple of 8 + for compatibility with 64-bit systems. + + * fix smb_ApplyV3DirListPatches to properly apply the hidden + attribute to dotfiles when the infoLevel < 0x101 and + cm_SyncOp has failed. + + * Fix the Freelance registry initialization code. There + was a possibility that some systems could end up with + garbage in the registry during a clean install. + Since 1.3.66: * file and directory names beginning with "." will now be given the hidden attribute when the volume access is anonymous. this matches Index: openafs/doc/txt/winnotes/afs-install-notes.txt diff -c openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.1 openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.2 *** openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.1 Tue Aug 10 00:10:44 2004 --- openafs/doc/txt/winnotes/afs-install-notes.txt Mon Aug 23 11:54:34 2004 *************** *** 1,4 **** ! OpenAFS for Windows 1.3.70 Installation Notes --------------------------------------------- The OpenAFS for Windows product was very poorly maintained throughout the --- 1,4 ---- ! OpenAFS for Windows 1.3.71 Installation Notes --------------------------------------------- The OpenAFS for Windows product was very poorly maintained throughout the *************** *** 97,103 **** (\Program Files\OpenAFS\Client\CellServDB). ! 5. OpenAFS for Windows 1.3.70 only supports Windows 2000, Windows XP, and Windows 2003. Windows NT 4.0 and the entire Windows 9x/Me line are no longer supported. Older releases of OpenAFS are available for download if those operating systems must be supported. The last version with support --- 97,103 ---- (\Program Files\OpenAFS\Client\CellServDB). ! 5. OpenAFS for Windows 1.3.71 only supports Windows 2000, Windows XP, and Windows 2003. Windows NT 4.0 and the entire Windows 9x/Me line are no longer supported. Older releases of OpenAFS are available for download if those operating systems must be supported. The last version with support *************** *** 216,224 **** No commandline arguments means authenticate to the local cell. ! 11. The AFS Server functionality provided with OpenAFS 1.3.70 might work but should be considered highly experimental. It has not been thoroughly tested. ! Any data which would cause pain if lost should be stored in an OpenAFS Server on Windows. A few notes on the usage of the AFS Client Service if it is going to be --- 216,224 ---- No commandline arguments means authenticate to the local cell. ! 11. The AFS Server functionality provided with OpenAFS 1.3.71 might work but should be considered highly experimental. It has not been thoroughly tested. ! Any data which would cause pain if lost should not be stored in an OpenAFS Server on Windows. A few notes on the usage of the AFS Client Service if it is going to be *************** *** 265,271 **** is often referred to as "fcrypt" mode. ! 18. OpenAFS 1.3.70 adds support for authenticated SMB connections using either NTLM or GSS SPNEGO (NTLM, Kerberos 5, ...). In previous versions of OpenAFS the SMB connections were unauthenticated which left open the door for several security holes which could be used to obtain access to --- 265,271 ---- is often referred to as "fcrypt" mode. ! 18. OpenAFS 1.3.71 adds support for authenticated SMB connections using either NTLM or GSS SPNEGO (NTLM, Kerberos 5, ...). In previous versions of OpenAFS the SMB connections were unauthenticated which left open the door for several security holes which could be used to obtain access to *************** *** 337,347 **** --- 337,357 ---- will result in AFS not running properly. The AFS Server should not be installed on a machine with Terminal Server installed. + 24. AFS is a Unix native file system. As such the OpenAFS client attempts to treat the files stored in AFS as they would be on Unix. File and directory names beginning with a "." are automatically given the Hidden attribute so they will not normally be displayed. + + 25. As of 1.3.71, the OpenAFS for Windows client supports a local Windows + authorization group called "AFS Client Admins". This group is used in + place of the "Administrators" group to determine which users are allowed + to modify the AFS Client Service configuration via either afs_config.exe + or fs.exe. During installation this group is created and the current + contents of the Administrators group is copied. + + ------------------------------------------------------------------------ Reporting Bugs: Index: openafs/doc/txt/winnotes/afs-issues.txt diff -c openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.1 openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.3 *** openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.1 Tue Aug 10 00:10:44 2004 --- openafs/doc/txt/winnotes/afs-issues.txt Mon Aug 23 11:54:34 2004 *************** *** 175,198 **** 12. miscellaneous 13. need to add support for all of the new registry values since 1.2.8 11. Identify why 16-bit DOS applications executed out of AFS fail ! 12. Create new Windows Security Group to which users can be added for them to become AFS ! Client Administrators ! 13. Add support for configurable Icon file representing AFS folders within the Explorer Shell ! 14. Documentation Documentation Documentation ! 15. Large File support (> 2GB) ! 16. Integrate KFW installation into the NSIS installer ! 17. Add support for record locking to AFS (requires changes to the servers) ! 18. Unicode enable the SMB/CIFS server. OEM Code Pages: 1. prevent the use of interoperable file names 2. force the use of paths no longer than 256 characters 3. force share names to be no longer than 13 characters 4. restrict authentication to ASCII only names and passwords ! 19. Complete implementation of CIFS Remote Administration Protocol ! 20. Correct the problems with overlapped writes which adversely affect Microsoft Office applications storing documents and temporary files within AFS volumes ! 21. Add support for SMB/CIFS Digital Signatures ! 22. Development of afsmap.exe tool to provide AFS aware NET USE functionality afsmap.exe [/PERSISTENT] afsmap.exe [/PERSISTENT] afsmap.exe /DELETE --- 175,198 ---- 12. miscellaneous 13. need to add support for all of the new registry values since 1.2.8 11. Identify why 16-bit DOS applications executed out of AFS fail ! 12. Add support for configurable Icon file representing AFS folders within the Explorer Shell ! 13. Documentation Documentation Documentation ! 14. Large File support (> 2GB) ! 15. Integrate KFW installation into the NSIS installer ! 16. Add support for record locking to AFS (requires changes to the servers) ! 17. Unicode enable the SMB/CIFS server. OEM Code Pages: 1. prevent the use of interoperable file names 2. force the use of paths no longer than 256 characters 3. force share names to be no longer than 13 characters 4. restrict authentication to ASCII only names and passwords ! 18. Complete implementation of CIFS Remote Administration Protocol ! 19. Correct the problems with overlapped writes which adversely affect Microsoft Office applications storing documents and temporary files within AFS volumes ! 20. Add support for SMB/CIFS Digital Signatures ! 21. Development of afsmap.exe tool to provide AFS aware NET USE functionality afsmap.exe [/PERSISTENT] afsmap.exe [/PERSISTENT] afsmap.exe /DELETE + 22. Write-through caching appears to be unsupported. Files copied to AFS + do not end up in the local cache.