[OpenAFS] krb5 inclusion in client build = NO kaserver auth whatsoever?

Jeff Blaine jblaine@kickflop.net
Mon, 03 Dec 2007 10:16:44 -0500

I'm trying to deduce the depth of effect from building
OpenAFS client tarballs with '--with-krb5-conf=...'

During our transition to krb5 auth, I'd like our clients
to have an OpenAFS allowing kaserver auth, but I obviously
want aklog in place for those willing to test krb5 + aklog.

Can anyone save me some testing time and comment on the
fesibility of that?