Re: A83: Ti uses MD5

Re: A83: Ti uses MD5

• To: <assembly-83@lists.ticalc.org>
• Subject: Re: A83: Ti uses MD5
• From: "David Phillips" <david@acz.org>
• Date: Fri, 1 Sep 2000 01:44:48 -0600
• References: <000101c012aa$2ca31740$3f08e4d5@cygnus-h1> <39ADC91A.807B3140@calc.org> <003b01c01344$8bf70720$0200a8c0@pc2> <39AEC48A.9F6B78AD@calc.org>
• Reply-To: assembly-83@lists.ticalc.org

As he said in his original email, and as is explained in the RFC, those are
not dynamic values.  They are what the registers are initialized to when
calculating an MD5 hash.  They must be the same for all implementations that
wish to generate the same hash value for the same input data.  If the hash
values are not consistent, then the algorithm is worthless.  There's no real
reason why not to comply with the RFC.  Doing so just makes everything
easier.

Btw, where are you going to find a z80 implemenation of MD5 to borrow?  If
you know, please let me know :)

> My problem with that is that generally you don't keep dynamic values in
> rom just for sheer RFC compliance (which I find hard to believe). The
> only way I would agree with that is if they got the routine from someone
> else and just added it, or that those values have to be the initial
> values for the md5-digest to work... but hey, whatever works. If it is
> true, then what do you plan to do with this knowledge?

• From:
• From:
• From:
• From:

• Prev: A83: ConvOP1
• Next: A83: Re: MD5
• Index(es):
  • Main
  • Thread