-This file is a rough list of known issues with the 1.3.63 release of OpenAFS
+This file is a rough list of known issues with the 1.3.70 release of OpenAFS
on Windows. This list is not complete. There are probably other issues
which can be found in the RT database or on the mailing list.
(1) File/Directory access is not integrated with windows security
-(2) tokens are assigned to the service on a system global basis. Therefore,
-all users and processes on the machine are able to access files with the
-list of available tokens. This is dangerous if anonymous logins are enabled;
-or if multiple users are on the machine (ie, Terminal Server or XP user
-switching)
-
(3) SMB LANA list is static.
(3a) IP address changes cause the service to terminate due to an assertion
and RX protocol operations. There was also an issue with large numbers of
page faults which have since been fixed.
-(5) The AFS SMB code logs numerous 1002 events each day. This is caused
-when an invalid SMB message are being processed from within the client.
-It is unclear if the invalid SMB message has been received or is being sent.
-
-(6) The AFS client service causes MRxSMB to produce 3019 events. This is probably
-the result of either malformed messages or invalid LANA values being used.
-
(7) There appear to be directory locking problems associated with renaming
directories.
be automatically prompted for different cells
(13) AFS Integrated Logon:
-(13a) Obtain tokens via Kerberos 5
(13b) If using Kerberos, need to figure out a means of passing credentials
into the user space until such time as I finish the new credential
cache service.
temporarily unable to access the Cell due to network restore timing
issues.)
-(18) No support for Unicode filenames. Translations make file unreadable
+(18) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent
+ the use of interoperable file names; force the use of paths no longer
+ than 256 characters; force share names to be no longer than 13
+ characters; restrict authentication to ASCII only names and passwords;
+ etc.
(19) No auto-restart on service failure
(20) Better EventLog handling
-(21) Named Pipes Support
+(21) Named Pipes Support [requires modifications to AFS servers to support]
(22) Memory Mapped File support
-(23) Large file support
-
-(24) Execution of debug builds indicates corruption of run time library
- allocated memory blocks due to buffer overruns. This may be the
- result of improper object locking or out of bounds access.
-
-(25) AFS Shell Extensions do not work on UNC paths of the form \\AFS\...
- They only work on mapped drives.
+(23) Large file support [both SMB/CIFS and AFS]
-(26) Implement persistent disk based cache which survives restarts
+(24) Implement persistent disk based cache which survives restarts
-(27) NSIS Installer issues
+(25) NSIS Installer issues
(a) integration with KFW install script
(b) Optional removal of AFS Server volumes
-(28) The User Interface needs to be re-designed to separate the per-user
+(26) The User Interface needs to be re-designed to separate the per-user
and per-machine settings. All of the new registry items need to
be added to the UI
-(29) Windows XP SP2 and Windows 2003 SP1 are going to lockdown the
- machine. We need to add code to programatically open the
- Internet Connection Firewall to the ports needed by the various
- AFS services.
-
-(30) It has been discovered that there is a lack of proper thread locking
- when "crypt" mode is used on Windows. This can be reproduced by
- performing multiple read operations simultaneous. The symptoms will
- be a memory followed by an eventual crash resulting from a stack
- overwrite. First step is to enable the use of RX_ENABLE_LOCKS when
- building on Windows.
-
-(31) There are remaining issues with the Freelance support. There appears
- to be an initialization issue related to whether the Freelance fake
- root.afs is constructed before or after the first access to a cell
- name via \\afs\cellname\. Accessing \\afs\cellname via cmd.exe
- appears to trigger the problem on a regular basis whereas 4nt.exe
- does not.
-
-
+(27) There appears to be a thread safety issue in the Rx library when
+ running on Intel processors which support hyper-threading
+
+(28) Thread initialization versus Global Drive Mapping. There is no
+ mechanism in the afsd_init.c to ensure that all of the threads
+ complete initializing in the correct sequence. In the case of
+ Global Drive Maps this is a problem because the Global Drive Maps
+ can be executed prior to the completion of the SMB registration
+ and service thread initialization.
+
+(29) Should we allow the AFSCACHE file to be stored in the Virtual Paging
+ file as long as we do not support persistent caches?
+
+(30) CIFS Remote Administration Protocol implementation is incomplete.
+ Notifications are not made to requestors when the view of a file
+ or folder changes due to token acquisition; token expiration; or
+ token destruction
+
+(31) Microsoft Office appears to have trouble editing files of ~20MB
+ or larger from within AFS. Performance is particularly slow and
+ applications such as Word often crash upon saving the files.
+
+
+-------------------------------------------------------------------------
+List of unfunded projects:
+
+ 1. No longer use AFS Client Service "cell" as the default cell for individual users
+ 2. Re-write afsd_service.exe to perform synchronized thread startup and shutdown.
+ Currently there is no synchronization of thread creation which results in timing
+ conflicts; and there is no attempt to cleanly shutdown the service which causes
+ problems when restarting and prevents the implementation of a persistent cache
+ 3. Implement a persistent cache (requires item 2)
+ 4. Prevent panic situation when the root.afs volume is not reachable and
+ the AFS Client Server is not using Freelance mode
+ 5. Prevent panic situation when the IP address to which the SMB server is bound is removed
+ from the local machine's network configuration
+ 6. Identify and fix the problems with running the RX library on Hyperthreaded systems
+ 7. Add support for Named Pipes within the afs filesystem
+ (This is not currently a supported feature of AFS; it will require
+ changes to the servers as well as the clients.)
+ 8. Re-write afscreds.exe to support:
+ 1. choosing between Kerberos 5 and Kerberos 4 on a per principal basis
+ 2. providing users with the ability to map multiple cells to a single principal
+ 3. providing change password functionality on a per principal basis
+ 4. no longer include drive mapping
+ 5. configuration of afscreds startup options in shortcut
+ 9. Re-write afs_config.exe to be only "per user" functionality which does not require admin
+ privileges
+ 1. default cell and principal for the user
+ 2. drive mappings
+ 3. visibility of afs creds and setting of afs creds startup options
+ 10. Create new afs_admin.exe tool to be installed in the administrator folder (or use MMS)
+ which contains
+ 1. afs client service cell name
+ 2. integrated logon configuration
+ 3. Gateway configuration
+ 4. start/stop service
+ 5. global drive mapping
+ 6. submount management
+ 7. file/volume server preferences
+ 8. afs cells
+ 9. cache configuration
+ 10. diagnostics
+ 11. network configuration
+ 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 <drive> <afs-path> [/PERSISTENT]
+ afsmap.exe <drive> <unc-path> [/PERSISTENT]
+ afsmap.exe <drive> /DELETE
git://git.openafs.org / openafs.git / blobdiff