MD5 and SHA cracked/broken...
tim.peters at gmail.com
Sun Sep 12 23:57:55 CEST 2004
> Others may have received that correctly, but between some systems and mine
> '=' seems to get re-encoded as '=3D' (including in S and T).
I think that was on my end. Because the person I was replying to had
"a funny character" in their name, which I quoted, gmail decided to
use quoted-printable to encode my msg. Changing = to =3D, and
changing the funny character in the OP's name to =E1, should have been
the only changes that made. It remains curious that whatever you're
using to *read* the message didn't decode that, though.
More information about the Python-list