[OpenAFS] readonly/readwrite

[Russ Allbery]

Nathan Rawling <nrawling@firedrake.net> writes:

> It would definitely help. In my past experience, the /usr/afs/logs
> directory is largely only useful for the salvager logs. On rare occaison
> I've been able to get information out of the kaserver logs that was
> vaguely useful.

If you run kaserver with the -debug flag, it actually produces useful
logs.  If you patch it to convert IP addresses into a human-readable form,
it produces even more useful logs.  That's the way we've run our kaservers
for years.

> If someone creates/deletes/moves a volume, I'd like to know what
> principal authorized the move. Also, if permission is denied for an
> operation, I'd like to have the opportunity to log it.

> If someone stops/restarts processes through bos, that might be a nice
> thing to log too. 

> Overall, I'd like my server processes to have the ability to log
> *anything* that happens. But I'd definitely like to be able to log
> administrative activity that affects volumes, user accounts, or server
> processes.

Definitely agreed.

> My guess is that the AFS logging has always been directed towards
> diagnosing problems with the code, not auditing malicious users/admins.

That's my impression too.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>