Did you read the spec? A very important thing to note here regarding the portrayed-as-heinous use of Kerberos by MS is that the standard does not introduct interoperability problems. It makes use of existing data storage in the Kerberos exchange structure (that means, in the spec to begin with) to store NT authentication crap. That NT authentication crap is very useful to NT/2k servers who might wish to perform authentication at several levels (store the whole NT authentication structure in a strongly-authenticatable Kerberos exchange). They haven't destroyed the spec, mutilated it, or hurt it. In fact, all they've done is copyright the specification for what they did to it, which describes some parts of the NT auth structure which probably falls under other copyights which they're trying to protect. Long story short: before we get all frothy-mouthed about MS's extensions, take a look at the material itself and consider why it's done and whether it actually "breaks" Kerberos.
Slashdot Mirror
Did you read the spec? A very important thing to note here regarding the portrayed-as-heinous use of Kerberos by MS is that the standard does not introduct interoperability problems. It makes use of existing data storage in the Kerberos exchange structure (that means, in the spec to begin with) to store NT authentication crap. That NT authentication crap is very useful to NT/2k servers who might wish to perform authentication at several levels (store the whole NT authentication structure in a strongly-authenticatable Kerberos exchange). They haven't destroyed the spec, mutilated it, or hurt it. In fact, all they've done is copyright the specification for what they did to it, which describes some parts of the NT auth structure which probably falls under other copyights which they're trying to protect. Long story short: before we get all frothy-mouthed about MS's extensions, take a look at the material itself and consider why it's done and whether it actually "breaks" Kerberos.