[202] in Kerberos
Re: quad_cksum failures.
jon@ATHENA.MIT.EDU (jon@ATHENA.MIT.EDU)
Sun Aug 9 21:41:25 1987
From jis@BITSY.MIT.EDU Wed Jul 8 13:39:56 1987
Date: Wed, 8 Jul 87 13:38:42 EDT
From: Jeffrey I. Schiller <jis@BITSY.MIT.EDU>
To: jbloom@ATHENA.MIT.EDU
Cc: Saltzer@ATHENA.MIT.EDU, Geer@ATHENA.MIT.EDU, Treese@ATHENA.MIT.EDU,
kerberos@ATHENA.MIT.EDU
In-Reply-To: jbloom@ATHENA.MIT.EDU's message of Wed, 8 Jul 87 12:35:45 EDT <8707081635.AA14812@PARIS.MIT.EDU>
Subject: Re: quad_cksum failures.
Well there are two issues with the network byte order:
1) How the result is expressed.
2) How it is computed.
(1) should be obvious. However issue two comes up because the
algorithm looks at the byte stream as if it were a collection of 16
bits integers.
As a practical matter I am planning to fix this by having the
RT code emulate the VAX code (ie. VAX byte order). This is because
there is already production code running on many vaxes in our
environment. I might do this and rename the function at the same time
to be "broken_quad_cksum" and have quad_cksum behave properly in a
later release.
-Jeff
