Re: XAuth vendor id

["Stephane Beaulieu" <stephane@xxxxxxxxx>]

Hey Andrew,

In Xauth (v5, I think).  I wrote that the VID is a MD5 of
"draft-ietf-ipsec-xauth-05.txt" or something like that.   And then I also
included the actual truncated hex output of the hash. --> 0x09002689dfd6b712

Turns out the code I wrote to generate the hash had a bug in it.  I think it
was that I only hashed the first 4 bytes of the string instead of the entire
string.

Anyways, I then removed the part that says: Hash this string, and now the
draft just says use 0x09002689dfd6b712, since most people were just using
that anyways.

So, the moral of the story is, never add 2 definitions for one item,
especially, when they are different. :)

Sorry for the inconveniance...
Stephane.






----- Original Message -----
From: "Andrew Krywaniuk" <andrew.krywaniuk@xxxxxxxxxxx>
To: <ietf-xauth@xxxxxxxx>
Sent: Tuesday, January 30, 2001 7:43 PM
Subject: XAuth vendor id


> Hi,
>
> The latest XAuth draft (00) specifies a vendor id of 0x09002689dfd6b712.
> However, I have a locally stored copy of a previous version (06) which
says
> that the vendor id is 0x228726e54acd6765.
>
> Has anyone out there deployed products with this vendor id? And are there
> any known compatibility issues which precipitated the change?
>
> Andrew
> -------------------------------------------
> Upon closer inspection, I saw that the line
> dividing black from white was in fact a shade
> of grey. As I drew nearer still, the grey area
> grew larger. And then I was enlightened.
>
>