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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <007601c41203$f6926e50$022d6e0c@default>
From: epic at hack3r.com (Epic)
Subject: Signal to Noise Ratio for February

Lately the SNR wouldn't allow for minimal communications if this were
any communications infrastructure.

-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of flatline
Sent: Wednesday, March 24, 2004 4:45 PM
To: Gregory A. Gilliss; full-disclosure@...ts.netsys.com
Subject: Re: [Full-Disclosure] 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 ]  

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html