OpenAFS 1.5.57 (Development branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News OpenAFS 1.5.57 (Development branch)
# 1  
Old 01-25-2009
OpenAFS 1.5.57 (Development branch)

AFS is a distributed filesystem which offers a client-server architecture, transparent data migration abilities, scalability, a single namespace, and integrated ancillary subsystems. License: IBM Public License Changes:
afs_config.exe on Windows was fixed. In Linux, a race during file truncation has been corrected. Linux 2.6.29 and MacOS 10.3 (fixed) and OpenBSD 4.4 are supported. The code was fixed to compile on newer OpenSolaris versions. On all client platforms, the userspace AFS library now supports large files when supported by the platform. Reconnection with Disconnected AFS works in more circumstances. On all server platforms, Salvager no longer attempts to recreate headers in the wrong partition. Volumes are properly marked in use on creation. On all platforms, the documentation was updated, and further race conditions in Rx were corrected. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
NOAUTH(5)							AFS File Reference							 NOAUTH(5)

NAME
       NoAuth - Disables authorization checking

DESCRIPTION
       The NoAuth file, if present in a server machine's /var/lib/openafs/local directory, indicates to the AFS server processes running on the
       machine that it is not necessary to perform authorization checking. They perform any action for any user who logs into the machine's local
       file system or issues a remote command that affects the machine's AFS server functioning, such as commands from the AFS command suites.
       Because failure to check authorization exposes the machine's AFS server functionality to attack, there are normally only two circumstances
       in which the file is present:

       o   During installation of the machine, as instructed in the OpenAFS Quick Start Guide.

       o   During correction of a server encryption key emergency, as discussed in the OpenAFS Administration Guide.

       In all other circumstances, the absence of the file means that the AFS server processes perform authorization checking, verifying that the
       issuer of a command has the required privilege.

       Create the file in one of the following ways:

       o   By issuing the bosserver initialization command with the -noauth flag, if the Basic OverSeer (BOS) Server is not already running.

       o   By issuing the bos setauth command with off as the value for the -authrequired argument, if the BOS Server is already running.

       To remove the file, issue the bos setauth command with "on" as the value for the -authrequired argument.

       The file's contents, if any, are ignored; an empty (zero-length) file is effective.

SEE ALSO
       bos_setauth(8), bosserver(8)

COPYRIGHT
       IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

       This documentation is covered by the IBM Public License Version 1.0.  It was converted from HTML to POD by software written by Chas
       Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

OpenAFS 							    2012-03-26								 NOAUTH(5)