1 This file is a rough list of known issues with the 1.4.0000 release of OpenAFS
2 on Windows. This list is not complete. There are probably other issues which
3 can be found in the RT database or on the mailing list.
6 (1) File/Directory access is not integrated with windows security
8 (3) SMB LANA list is static.
10 (3a) IP address changes cause the service to terminate due to an assertion
11 in smb_Listener() thread.
13 (3b) New IP addresses do not get bound to the SMB server
15 (3c) Loopback adapter hack:
16 (i) prevents use of AFS Gateway
17 (ii) requires installation of loopback adapter
18 (iii) the list of hack adapters is incomplete (VMWare, MS TV/Video, ...)
19 (iv) incompatible with Windows 2000 and earlier
21 (9) Convert to IFS!!!!!!
23 (10) Kerberos 5 integration:
24 (10f) allow arbitrary cell to realm mappings
25 (10g) modify UI to allow user to choose whether to authenticate
27 (10h) modify UI to allow user to select an existing principal to
28 be used to request AFS tokens
29 (10i) modify UI to display Kerberos 5 ticket info (principal,
30 ticket lifetimes, etc)
32 (11) Default cell is system global just like everything else. Different
33 users logging in via Integrated Logon or using afscreds.exe cannot
34 be automatically prompted for different cells
36 (12) AFS Integrated Logon:
37 (12b) If using Kerberos, need to figure out a means of passing credentials
38 into the user space until such time as I finish the new credential
40 (12c) If network is not available must store the username and password
41 somewhere until such time as the network starts.
43 (13) If a drive mapping is "in use", then afscreds cannot be used to Modify
44 or Delete the Mapping. If a map to "H:" to \afs\cell\foo" with
45 description "home" is modified to point to \afs\cell\bar, then the
46 description must be unique. "home" cannot be reused. We need a way
47 to remove "home" from the submount list.
49 [Actually, an end user should not be able to modify the submount list]
51 (14) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent
52 the use of interoperable file names; force the use of paths no longer
53 than 256 characters; force share names to be no longer than 13
54 characters; restrict authentication to ASCII only names and passwords;
57 (15) No auto-restart on service failure
59 (16) Better EventLog handling
61 (17) Named Pipes Support [requires modifications to AFS servers to support]
63 (18) Memory Mapped File support
65 (19) Large file support [both SMB/CIFS and AFS]
67 (20) NSIS Installer issues
68 (a) integration with KFW install script
69 (b) Optional removal of AFS Server volumes
71 (21) The User Interface needs to be re-designed to separate the per-user
72 and per-machine settings. All of the new registry items need to
75 (22) CIFS Remote Administration Protocol implementation is incomplete.
76 Notifications are not made to requestors when the view of a file
77 or folder changes due to token acquisition; token expiration; or
80 (23) Remove submount creation as a side effect of AFS drive mapping.
82 The AFS Submount is effectively a server side alias for a path
83 located in the AFS space. This alias is exported by the AFS
84 SMB/CIFS Server to the Windows SMB/CIFS client as a Share name.
85 This makes the AFS Submount a system global setting which should
86 only be modified by a member of the "AFS Client Admin" group.
88 afs_creds.exe and afs_config.exe should be modified to no longer
89 use submount names when creating drive maps. Drive maps should
90 simply use the full AFS path name. Submounts should not be
91 created as a side effect of a drive mapping.
93 The creation of submounts should only be possible via afsshare.exe
94 or by the new AFS Client Service Administration tool when executed
95 by an authorized user.
97 (24) No support for byte range locking (or locking at all)
99 -------------------------------------------------------------------------
100 List of unfunded projects:
102 1. No longer use AFS Client Service "cell" as the default cell for individual users
103 2. Prevent panic situation when the root.afs volume is not reachable and
104 the AFS Client Server is not using Freelance mode
105 3. Prevent panic situation when the IP address to which the SMB server is bound is removed
106 from the local machine's network configuration
107 4. Add support for Named Pipes within the afs filesystem
108 (This is not currently a supported feature of AFS; it will require
109 changes to the servers as well as the clients.)
110 5. Re-write afscreds.exe to support:
111 1. choosing between Kerberos 5 and Kerberos 4 on a per principal basis
112 2. providing users with the ability to map multiple cells to a single principal
113 3. providing change password functionality on a per principal basis
114 4. no longer include drive mapping
115 5. configuration of afscreds startup options in shortcut
116 6. Re-write afs_config.exe to be only "per user" functionality which does not require admin
118 1. default cell and principal for the user
119 2. drive mappings but no submounts
120 3. visibility of afs creds and setting of afs creds startup options
121 7. Create new afs_admin.exe tool to be installed in the administrator folder (or use MMS)
123 1. afs client service cell name
124 2. integrated logon configuration
125 3. Gateway configuration
126 4. start/stop service
127 5. global drive mapping
128 6. submount management
129 7. file/volume server preferences
131 9. cache configuration
133 11. network configuration
135 13. need to add support for all of the new registry values since 1.2.8
136 8. Identify why 16-bit DOS applications executed out of AFS fail
137 9. Add support for configurable Icon file representing AFS folders within the Explorer Shell
138 10. Documentation Documentation Documentation
139 11. Large File support (> 2GB) in SMB/CIFS client
140 12. Integrate KFW installation into the NSIS and MSI installers
141 13. Add support for byte range locking to AFS (requires changes to the servers)
142 14. Unicode enable the SMB/CIFS server. OEM Code Pages:
143 1. prevent the use of interoperable file names
144 2. force the use of paths no longer than 256 characters
145 3. force share names to be no longer than 13 characters
146 4. restrict authentication to ASCII only names and passwords
147 15. Complete implementation of CIFS Remote Administration Protocol
148 16. Add support for SMB/CIFS Digital Signatures
149 17. Development of afsmap.exe tool to provide AFS aware NET USE functionality
150 afsmap.exe <drive> <afs-path> [/PERSISTENT]
151 afsmap.exe <drive> <unc-path> [/PERSISTENT]
152 afsmap.exe <drive> /DELETE
153 18. Missing SMB/CIFS functions:
161 19. StoreBehind mode is not implemented. Or more correctly, all data is
162 written directly to the server and is not cached. Writes invalidate
163 the local cache entries which are then read back from the server.
164 20. Develop an optional Installable File System replacement for the SMB/CIFS
166 21. Add support for storing Extended Attributes on files
167 22. Add support for storing Windows ACLs on files
168 23. Remove submount creation as a side effect of drive creation
169 24. Finish conversion from string.h to strsafe.h for VS.NET 2005
170 25. Implement RX Statistics gathering interfaces and reporting tools
171 (necessary to obtain profiling data)
172 26. Implement RX Connection Pools in the Cache Manager allowing more than
173 four simultaneous requests to a single server to be processed at a time