update-winnotes-20040511

Update the changes and issues files for the 1.3.64 release
This commit is contained in:
Jeffrey Altman 2004-05-11 21:08:57 +00:00 committed by Jeffrey Altman
parent ce5e3e99d7
commit a2c0be0661
2 changed files with 106 additions and 4 deletions

View File

@ -1,3 +1,90 @@
Since 1.3.63:
* afsd_service.exe will now display a message box to the
desktop when it terminates due to an IP Address Change.
* installer no longer deletes AFS Server configuration data
on uninstall
* installer generates a warning dialog if the RPC service
is not properly configured
* installer compressed with lzma instead of bzip2
* afsd_service.exe shutdown crash solved once and for all
* reference counting of smb_vc_t data structures improved
* name space collision of smb_fid_t event objects corrected
* the output of "fs memdump" is now written to
%WINDIR%\TEMP\afsd_alloc.log
* the file TaAfsApp_1033.dll is now properly installed allowing
the User Manager to start
* a new algorithm is used for computing filename pattern matches
* afscreds.exe now accepts user names containing instance
fields.
* Fix the Directory Name Lookup Cache to be case-sensitive.
This is crucial in environments in which a Windows client
is accessing a directory with more than one filename that
differs only by case. If the directory contains "FOO"
and "Foo". You want "DEL Foo" to delete the correct one.
We still have a problem in that "DEL foo" will delete a
random filename. This will be addressed in a future release.
* Fix afscreds.exe -M option (renewMaps) to work when High
Security mode is off. Also, remember to disable the ActiveMap
flag in afsdsbmt.ini when a drive mapping is removed.
* Updates to NSIS installer script. AFS Server configuration
data will not be destroyed on un-install or re-install.
Use a better compression algorithm.
* afslogon.dll now uses KFW to obtain tokens when available
* afslogon.dll when given an all uppercase username will
attempt to authenticate with both the uppercase name
and an all lowercase variation
* DST modification removed. The fix appears to make things
worse after a reboot of the machine.
* fs.exe: added "cscpolicy" which is used to
change client side caching policy for AFS shares
Usage: fs cscpolicy [-share <AFS share>] [-manual] [-programs]
[-documents] [-disable] [-help]
* Several uninitialized variables have been initialized
* It is now possible to obtain tokens using cross realm
Kerberos within afscreds.exe:
cell: dementia.org
user: jaltman@ATHENA.MIT.EDU
password: xxxxxxxx
Will obtain a cross realm ticket for jaltman/DEMENTIA.ORG@ATHENA.MIT.EDU
will will in turn be used to obtain afs@DEMENTIA.ORG.
The resulting token will be stored with the display name
jaltman@ATHENA.MIT.EDU@dementia.org
* aklog.exe has been added to the client
Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
[[-p | -path] pathname]
[-noprdb] [-force]
[-5 | -4]
-d gives debugging information.
krb_realm is the kerberos realm of a cell.
pathname is the name of a directory to which you wish to authenticate.
-noprdb means don't try to determine AFS ID.
-5 or -4 selects whether to use Kerberos V or Kerberos IV.
(default is Kerberos V)
No commandline arguments means authenticate to the local cell.
Since 1.3.62:
* All of the resource files have been restructured to adhere to
a set of rules IBM implemented for loading string resources.

View File

@ -117,10 +117,9 @@ directories.
(26) Implement persistent disk based cache which survives restarts
(27) NSIS Installer issues for re-installs
(a) AFS Server Configurator should not start on update
(b) AFS Server Volumes and Configuration Data should not be
removed on uninstall
(27) 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
and per-machine settings. All of the new registry items need to
@ -130,3 +129,19 @@ directories.
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.