Well, that was Derek's opinion. And now, presenting an alternate
viewpoint on the kaserver....
Frankly, CMU uses the kaserver for generic Kerberos use. The number
of "compatibility" problems are practically nil.
CMU uses the kaserver to issue tickets for:
AFS
Zephyr
printing
on-line library lookups
remote logins
remote process monitoring
The only problem I personally ever had with the kaserver was trying to
run it on a DECstation. The byte-order for the IP address in tickets
was wrong . This led to authentication failures for Zephyr (but not
AFS, because it ignores the IP address <sigh>). I know that CMU's ECE
department patched the kaserver, but I don't know if Transarc fixed
this in their release yet.
Please note that Zephyr is actually a product MIT's Athena project and
works just fine in CMU's environment. (Well, if you excuse some
bogosities in the Zephyr code.)
-Jay Laefer
