Hi Jeff: Am 22.03.17 20:39 schrieb(en) Jeffrey Stedfast:
Hah, I actually just converted it to use GChecksum internally a few days ago…
I recall that you had your own md5 implementation in 2.6, didn't you?
I didn’t make it generic though, it’s still MD5-only because that was its only use-case (for calculating/verifying the Content-Md5 header value). I could make it generic, though, if you are using it for other things?
As with some of my other ideas (like parser error tracking), this is basically for message analysis (spam etc.), not for Balsa. Write a message part (suspicious attachment) to a stream so it can be fed into other tools, and during this process create a sha256 hash which can be checked against a (spam, malware, ...) data base. Unfortunately, md5 or sha1 is not sufficient any more there days, see the stunning demonstration at <https://alf.nu/SHA1> producing two completely different pdf's with *the same* sha1 hash (similar tools are around for md5 since some time). Cheers, Albrecht.
pgpFBV2Qrmzaz.pgp
Description: PGP signature
_______________________________________________ balsa-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/balsa-list
