[OpenAFS] Re: Any budding documentation writers
Wed, 03 Mar 2010 10:28:04 -0800
Simon Wilkinson <email@example.com> writes:
> It might be, but I think documenting multiple ways of doing things is
> likely to be confusing to a novice user. We should pick one mechanism
> and stick to it, and aklog is probably the best one to choose. In
> addition, klog.krb5 won't be applicable to rxgk, but aklog is.
Why wouldn't klog.krb5 be applicable to rxgk, at least in the abstract
(doing the work is another matter)? It's just the combination of a kinit
and aklog without storing the credentials in the file system. It should
be usable with any Kerberos-based authentication mechanism.
Of course, implementing basically the same code in both aklog and
klog.krb5 isn't a particularly good idea, and ideally the token-getting
code should move into a library that both of them should call, but I think
that's a Simple Matter of Programming.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>