I have been helping out with SSL and I was using some of my
SqueakElib code with runs with the original SqueakMap version of the
Crypto library. I was installing the MAC layer which uses SHA1. I
then ported it to the new Crypto libraries and it broke on SHA1 use.
It seems the new SHA1 is returning integers instead of the
traditional byte arrays and this is a problem, don''t you think? It
is now inconsistent with MD5. Crypto should operate on byte arrays
and all conversion should be in the application. Even if the input
is a byte array, it returns an integer. So I was just wondering what
the deal was and whether we can get it changed back.