On Fri, Nov 6, 2009 at 3:13 PM, Marcus Watts <[email protected]> wrote:
>> Marcus has also summarised the issues to the afs3-stds list, along >> with his feelings of how desirable / achievable each feature might be: >> >> http://michigan-openafs-lists.central.org/archives/afs3-standardization/2009-Oc >> tober/000512.html >> >> (There are additional issues, beyond those from the hackathon, on that >> list - in particular, many sites indiciated at the Rome Workshop that >> a flag day transition to rxk5 would not be achievable for them) >> >> S. > > I should comment a bit about timeline. > > At the hackathon, it turns out the openafs gatekeepers have a schedule > whereby 1.6 comes out in "6 months", and nothing regarding improved > security mechanisms can happen "to the mainline" before then. So that > schedule has nothing to do with rxk5; it's an absolute constraint. Apparently code revision system branches were invented recently or something. You should check them out. They're awesome. Derrick with equivalent disingenuous skills to the next guy _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
