full-disclosure - All the md5 hashes in every single update message sent to this list

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <0428856A-CACA-445A-9289-62977561E34C@b1towel.com>
Date: Sat, 16 Oct 2010 02:22:24 -0400
From: B1towel <ben@...owel.com>
To: "full-disclosure@...ts.grok.org.uk" <full-disclosure@...ts.grok.org.uk>
Subject: All the md5 hashes in every single update message
	sent to this list

What is the purpose of all the patch notification emails that when a security vulnerability is fixed the people who send out the notification email include a 5 mile long list of md5 hashes for every single package and all dependancies for the package that was updated? I feel that information does not need to be in the notification that the latest version fixed a security vulnerability, and to me it just gets in the way of reading the occasionally useful content this list has to offer.
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/