full-disclosure - A CALL FOR FULL-DISCLOSURE TO BECOME A MODERATED 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1c3fa2270512150839m54e75e17t1a34e4d8abc375bb@mail.gmail.com>
Date: Thu Dec 15 16:39:54 2005
From: yahooinsider at gmail.com (Joe Average)
Subject: A CALL FOR FULL-DISCLOSURE TO BECOME A
	MODERATED LIST

On 12/15/05, uber@...h.com <uber@...h.com> wrote:
>
> I WOULD JUST LIKE TO EXPRESS MY DEEP SUPPORT FOR THIS IDEA.  MAKING
> THE LIST MODERATED WOULD REALLY HELP MY JOB AS A SECURITY
> RESEARCHER.  I COULD MAKE QUICKER, MORE WELL INFORMED CHOICES IN MY
> DAY TO DAY TASKS OF PEN TESTING LEGITIMATELY.  I WILL ONLY GET THE
> GOOD STUFF AND NONE OF THIS PISSING CONTEST WHICH IS KILLING THIS
> LIST.  MODERATING WOULD MAKE THE LIST MUCH MORE PROFESSIONAL AND
> WOULD BRING IT ONE STEP ABOVE SECURITY FOCUS.
>
> ONCE AGAIN.  I AM 150% FOR THE MODERATION OF FULL-DISCLOSURE.


no need,

a) ban all gmail addresses
b) ban nicknames (real name only)
c) start inforcing list policy for trouble makers who attack legitimate
researchers like netdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20051215/ef104762/attachment.html