On 06/15/2010 09:47 PM, Russ Allbery wrote:
* As we've stated for some time, at the point at which we release an OpenAFS 2.0 with rxgk, we intend to deprecate kaserver. What I believe that should mean is that, in OpenAFS 2.0, we will require passing a flag to configure to build kaserver and all the related code for Kerberos v4 support in the tree (kaserver, kas, kpasswd, the PAM modules, tokens.krb, pagsh.krb, klog, klog.krb, and doubtless some other things that we find hiding). Unless someone steps forward before that time and updates uss to make it useful in a non-kaserver environment, I believe we should disable building of uss at the same time. At that time, we will stop building that code for the binary distributions from openafs.org, and I will also stop building the client packages with that code in Debian (Debian never included kaserver). We will then remove that code entirely after (at least) a year after 2.0 is out, which if we stick with our intended time-based release practice will mean 2.4.
We're using uss in a non-kaserver environment. I know that we could do without it, but it's nice to have. If uss weren't available, an equivalent tool would need to be available.
Jason _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
