full-disclosure - Re: requesting info

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

Date: Wed, 25 Apr 2007 08:04:11 -0400
From: Tim <tim-security@...tinelchicken.org>
To: n n <s_x_dls@...mail.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: requesting info

> i'm just a new guy to this community...i was asking about the right 
> procedures that one should do when he/she discovers a vulnerability in and 
> application or operating system
> 
> also what is the right procedure to make in order to publish a new hacking 
> technique to that it's know by the name of the publisher

This is a topic of much debate, so you'll get lots of different answers.
Maybe people do rely on [1] for the basis of their disclosure policy,
though.

tim

1. http://www.wiretrip.net/rfp/policy.html

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/