full-disclosure - [inbox] Re: Full Disclosure "Code of conduct"

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]

Date: Sun May  7 04:07:34 2006
From: exibar at thelair.com (Exibar)
Subject: [inbox] Re: Full Disclosure "Code of conduct"



> -----Original Message-----
> From: n3td3v [mailto:n3td3v@...il.com]
> Sent: Saturday, May 06, 2006 10:21 PM
> To: full-disclosure@...ts.grok.org.uk
> Subject: [inbox] Re: [Full-disclosure] Full Disclosure "Code of conduct"
>
>
> On 5/7/06, Aaron Gray <angray@...b.net> wrote:
> >
> > I am suggesting that we all cooperate and produce a "Code of
> Conduct" for
> > participating on the Full Disclosure mailing list.
> >
> > Suggested start :-
> >
> >     1) No Swearing
> >     2) No slagging others off
> >     3) No selling of exploits and vulnerabilities
> >
>
> Lets add:
>
> 4) No Cross-site scripting and SQL injection advisories.
>
> We get the picture, theres 100 million flaws for
> guestbooks/bulletinboards and other unheard of vendor products. Its
> time to kill the cross-site scripting and sql injection spam created
> by copy & paste script kids. Let the lame Securityfocus Bugtraq
> mailing list get submitted with that B*S from now on.
>
>

Let add:

5) no posts from N3td3v or 0x80   (even though this last post by n3td3v was
actually an acceptable post)