[26] in Kerberos_V5_Development
thoughts on backwards compatibility
wesommer@ATHENA.MIT.EDU (wesommer@ATHENA.MIT.EDU)
Tue Jan 9 16:52:56 1990
Here's a proposal for backwards compatibility:
Kerberos version 5 uses a completely different data encoding than V4
(ASN.1 in V5 rather than an ad-hoc encoding in V4), and the position
of the version number in the header is different.
A subset of the V5 interfaces will recognise V4 protocol messages,
call a subset of the V4 library, and appropriately translate the
returns from the V4 library call into the V5 interface form. The
backwards compatibility code should be under an #ifdef, so it may be
disabled at compile time to remove the dependancy on kerberos V4.
The subset of V5 interfaces should be sufficient to allow servers to
support both V4 and V5 clients; New clients will always initiate the
use of the V5 protocol.
