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) Loopback adapter is not always installed without bindings to "File and
44 Printer Sharing for Microsoft Networks" and with bindings to "Client for Microsoft
45 Networks". If these are not bound correct then SMB names will successfully
46 be published to a list of zero which causes the AFS not to function.
47 We need a way to test whether the Loopback adapter is properly bound
48 so we know if it is safe to use. Actually, it is worse. Even with
49 the bindings on Win2000 the loopback adapter frequently fails to publish
50 SMB names. Of course, the error messages report nothing.
52 (14) If a drive mapping is "in use", then afscreds cannot be used to Modify
53 or Delete the Mapping. If a map to "H:" to \afs\cell\foo" with
54 description "home" is modified to point to \afs\cell\bar, then the
55 description must be unique. "home" cannot be reused. We need a way
56 to remove "home" from the submount list.
58 [Actually, an end user should not be able to modify the submount list]
60 (16) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent
61 the use of interoperable file names; force the use of paths no longer
62 than 256 characters; force share names to be no longer than 13
63 characters; restrict authentication to ASCII only names and passwords;
66 (17) No auto-restart on service failure
68 (18) Better EventLog handling
70 (19) Named Pipes Support [requires modifications to AFS servers to support]
72 (20) Memory Mapped File support
74 (21) Large file support [both SMB/CIFS and AFS]
76 (22) Implement persistent disk based cache which survives restarts
78 (23) NSIS Installer issues
79 (a) integration with KFW install script
80 (b) Optional removal of AFS Server volumes
82 (24) The User Interface needs to be re-designed to separate the per-user
83 and per-machine settings. All of the new registry items need to
86 (25) CIFS Remote Administration Protocol implementation is incomplete.
87 Notifications are not made to requestors when the view of a file
88 or folder changes due to token acquisition; token expiration; or
91 (26) Remove submount creation as a side effect of AFS drive mapping.
93 The AFS Submount is effectively a server side alias for a path
94 located in the AFS space. This alias is exported by the AFS
95 SMB/CIFS Server to the Windows SMB/CIFS client as a Share name.
96 This makes the AFS Submount a system global setting which should
97 only be modified by a member of the "AFS Client Admin" group.
99 afs_creds.exe and afs_config.exe should be modified to no longer
100 use submount names when creating drive maps. Drive maps should
101 simply use the full AFS path name. Submounts should not be
102 created as a side effect of a drive mapping.
104 The creation of submounts should only be possible via afsshare.exe
105 or by the new AFS Client Service Administration tool when executed
106 by an authorized user.
108 (27) No support for byte range locking (or locking at all)
110 -------------------------------------------------------------------------
111 List of unfunded projects:
113 1. No longer use AFS Client Service "cell" as the default cell for individual users
114 2. Prevent panic situation when the root.afs volume is not reachable and
115 the AFS Client Server is not using Freelance mode
116 3. Prevent panic situation when the IP address to which the SMB server is bound is removed
117 from the local machine's network configuration
118 4. Add support for Named Pipes within the afs filesystem
119 (This is not currently a supported feature of AFS; it will require
120 changes to the servers as well as the clients.)
121 5. Re-write afscreds.exe to support:
122 1. choosing between Kerberos 5 and Kerberos 4 on a per principal basis
123 2. providing users with the ability to map multiple cells to a single principal
124 3. providing change password functionality on a per principal basis
125 4. no longer include drive mapping
126 5. configuration of afscreds startup options in shortcut
127 6. Re-write afs_config.exe to be only "per user" functionality which does not require admin
129 1. default cell and principal for the user
130 2. drive mappings but no submounts
131 3. visibility of afs creds and setting of afs creds startup options
132 7. Create new afs_admin.exe tool to be installed in the administrator folder (or use MMS)
134 1. afs client service cell name
135 2. integrated logon configuration
136 3. Gateway configuration
137 4. start/stop service
138 5. global drive mapping
139 6. submount management
140 7. file/volume server preferences
142 9. cache configuration
144 11. network configuration
146 13. need to add support for all of the new registry values since 1.2.8
147 8. Identify why 16-bit DOS applications executed out of AFS fail
148 9. Add support for configurable Icon file representing AFS folders within the Explorer Shell
149 10. Documentation Documentation Documentation
150 11. Large File support (> 2GB) in SMB/CIFS client
151 12. Integrate KFW installation into the NSIS and MSI installers
152 13. Add support for byte range locking to AFS (requires changes to the servers)
153 13a. Simulate support for byte range locking at the client; use full locks
155 14. Unicode enable the SMB/CIFS server. OEM Code Pages:
156 1. prevent the use of interoperable file names
157 2. force the use of paths no longer than 256 characters
158 3. force share names to be no longer than 13 characters
159 4. restrict authentication to ASCII only names and passwords
160 15. Complete implementation of CIFS Remote Administration Protocol
161 16. Add support for SMB/CIFS Digital Signatures
162 17. Development of afsmap.exe tool to provide AFS aware NET USE functionality
163 afsmap.exe <drive> <afs-path> [/PERSISTENT]
164 afsmap.exe <drive> <unc-path> [/PERSISTENT]
165 afsmap.exe <drive> /DELETE
166 18. Missing SMB/CIFS functions:
174 19. StoreBehind mode is not implemented. Or more correctly, all data is
175 written directly to the server and is not cached. Writes invalidate
176 the local cache entries which are then read back from the server.
177 20. Develop an optional Installable File System replacement for the SMB/CIFS
179 21. Add support for storing Extended Attributes on files
180 22. Add support for storing Windows ACLs on files
181 23. Remove submount creation as a side effect of drive creation
182 24. Finish conversion from string.h to strsafe.h for VS.NET 2005