full-disclosure - Signal to Noise Ratio for February

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: <6.0.3.0.2.20040325004448.0248e920@mail.greyhat.nl>
From: flatline at greyhat.nl (flatline)
Subject: Signal to Noise Ratio for February

Gregory,

What makes you think F-D's "signal" would consist solely of advisories? If 
you've read the list charter 
(http://lists.netsys.com/full-disclosure-charter.html), you should know to 
not only filter on the word "advisory".

Your method of generating a signal:noise relation seems far from correct.

/ flatline

At 11:41 PM 24-03-2004, Gregory A. Gilliss wrote:
>List:
>
>Just for fun I decided to calculate the S/N ratio of FD. I used the
>data from February 2004 (the last full month available). Here's my
>methodology (for those who can do better :-):

[ snip ]