[1056] in Kerberos

home help back first fref pref prev next nref lref last post

Some questions on V5

daemon@ATHENA.MIT.EDU (Chuck McManis)
Sat Jul 14 05:07:33 1990

Date: Fri, 13 Jul 90 13:34:46 PDT
From: cmcmanis@Eng.Sun.COM (Chuck McManis)
To: kerberos@ATHENA.MIT.EDU


There is something weird here and for the life of me I can't figure
out what is really going on. It certainly looks bad, but I'd like to
have the "full story" before I make any conclusions.

Item. Kerberos V5 was accepted as part of the OSF DCE offerring with
      HP/Apollo changes. 

Item. The RFT process required that all submitted technology be "running"
      on June 1rst. Which makes sense because of their schedule to release
      DCE. 

Item. Presumably OSF has had something running that they are
      calling Kerberos since the 1st of June. Joe Pato made the 
      comment that HP/Apollo would probably keep their changes as
      a proprietary part of the OSF offerring (which is perfectly
      reasonable since it no doubt adds value).

Questions :

Where is the core part of this V5 Kerberos? (The V5 protocol engine)

Will V5 be OSF proprietary or will there be continue to be an MIT
open version?

Why can't we get any information on version 5? (Even the final
specification.)

Where is the V5 alpha so that people can make sure they aren't
depending on V4 features that may vanish?

If Kerberos didn't make the 1 June deadline for OSF does that
mean it is out of DCE?

Mumblings :

From the outside looking in, the appearance of a conspiracy to keep
Kerberos out of the hands of people who might ship it before OSF is
evident. I don't think anyone is that silly so I discourage such 
rumors whenever I hear them. What I would like is that the people
who keep talking about V5 in the present tense would let someone
else see it. How about a "final" spec even? 

Confused in Mountain View,

home help back first fref pref prev next nref lref last post