[OpenAFS-devel] Preliminary news file

Sam Hartman hartmans@mit.edu
16 Jun 2001 00:30:14 -0400


--=-=-=


Here is an attempt at a NEWS file for openafs.  Things I know I don't
have and can easily get docs for:

* bosserver restricted mode
* New Unix ports

Things I would like your help documenting:

* New Windows 95/98 port

Also, please indicate things I forgot about and should document.


--=-=-=
Content-Disposition: attachment; filename=afs-erata
Content-Description: AFS NEWS file

Openafs News -- history of user Visible changes. 15 June 2001

* Changes since Openafs 1.0

** A client system can now have multiple sysname values for @sys.
 They will be searched  in order when looking up files in AFS.  The
 -newsysname argument to fs sysname can be repeated to set multiple
 sysnames.

** A new system group is created  for new cells (system:ptsviewers
   with id -203).  If this group exists, members of this group can
   examine and read the entire protection database.  They can examine
   all users and groups and can get the membership of any group.


** A new program, pt_util has been added to the distribution.  This
   program allows users to print the contents of the protection
   database or to edit the protection database without running a
   ptserver.  It can be used to set up a new cell without ever running
   in noauth mode.  Run pt_util -h for help.

** The fs setcrypt and fs getcrypt commands have been added.  These
   commands allow the system administrator to require that the client
   encrypt all authenticated traffic between the client workstation
   and AFS.  The encryption used is weak, but is likely better than
   sending unencrypted traffic in most environments.  Some functions,
   such as looking for a volume may not be encrypted, but data
   transfer certainly is.  By default data is not encrypted.  At this
   time no significant experimentation with server performance has
   been conducted.

** If AFS is compiled with  AFS_AFSDB_ENV, then  the -afsdb option can
   be given to afsd on startup.  If this option is used, then new
   cells will be looked up using AFSDB records stored in DNS if they
   are not found in CellServDB.  This means that users can create
   cross-cell mountpoints in directories they control to  access cells
   not in root.afs, and that cells in root.afs need not be in the
   client's CellServDB.


** AFS database servers can be marked as read-only clones.  Surround
   the hostname in square brackets on the bos addhost command and the
   database server will never be elected sync site.  This is useful
   for cells distributed over a wide region.
--=-=-=--