full-disclosure - How to Report a Security Vulnerability to Microsoft

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 Apr 13 18:57:18 2005
From: steve at unixwiz.net (Steve Friedl)
Subject: How to Report a Security Vulnerability to
	Microsoft

On Wed, Apr 13, 2005 at 01:50:25PM -0400, bkfsec wrote:
> My point 
> is that the the researcher making the disclosure should determine their 
> timeline, but with obvious consideration of the vendor and users, but 
> that that should be a reasonable approach, and not followed because the 
> researcher is forced to follow it.

I agree completely: the vendor can have an opinion, but not a vote.

Steve

-- 
Stephen J Friedl | Security Consultant |  UNIX Wizard  |   +1 714 544-6561
www.unixwiz.net  | Tustin, Calif. USA  | Microsoft MVP | steve@...xwiz.net