Re: md5 version 2.0.4 to 2.0.5

Hi,

Clint wrote :
All,

I have noticed that since md5 has went to version 2.0.5 that I have
seen different results from previous versions of md5. I have older
apps that use md5 version 2.0.4 and if I upgrade md5 to 2.0.5., the
values return from the ::md5::md5 -hex command are different. For
example:

md5 v. 2.0.4:
-> ::md5::md5 -hex whatupwitdat
39054E44B13795EBC148CF17FE5ED22D

md5 v. 2.0.5
-> ::md5::md5 -hex whatupwitdat
2C9DEC74AE2AA10452D8820C117C6A4D

Anyone know if there is some new switch in version 2.0.5 for backward
compatible, or do I have to go back to all my old apps and rework if I
upgrade to version 2.0.5?

thanks,

md5sum is strictly defined, and must not change, neither from one version of md5 package to another, nor from tcllib's md5 implementation to other implementation. Correct digest for "whatupwitdat" is "3905...", so what you get with 2.0.5 is broken. However, using md5 2.0.5 from tcllib 1.10, I can't reproduce the problem you report, and get correct answer. So it looks like your md5 distrib is broken. Which platform are you running? Also, check if your md5 package falls back to one of the accelerator (critcl, cryptkit or trf) instead of the pure Tcl implementation.

Eric
.

Relevant Pages

  • Re: md5 version 2.0.4 to 2.0.5
    ... seen different results from previous versions of md5. ... version of md5 package to another, nor from tcllib's md5 implementation ... check if your md5 package falls back to one of the ... The 2.0.4 version I am using is on a Linux box using tcl 8.4.12. ...
    (comp.lang.tcl)
  • Re: md5 version 2.0.4 to 2.0.5
    ... Clint wrote: ... I have noticed that since md5 has went to version 2.0.5 that I have ... version of md5 package to another, nor from tcllib's md5 implementation ... instead of the pure Tcl ...
    (comp.lang.tcl)