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

Message-ID: <041120050656.26500.425A1F8D000619B00000678421602807410A9D0B0E039A9B979A9B@att.net>
Date: Mon Apr 11 07:56:41 2005
From: tuytumadre at att.net (tuytumadre@....net)
Subject: How to Report a Security Vulnerability to
	Microsoft

> 
> hahahahahaha 
> 
> m$ doing social engineering on fd, this is a joke. 
> 
> basically they want your 0days so billg becomes more rich. 
> 

Mr. Guninski, although I am a huge fan of your work, I could not disagree more. I am sending this email from Redmond where I was invited by Microsoft to a small conference about security (it was mostly about what they go through when stuff is reported). "M$", as you call it, is not trying to get your 0days. They simply want to protect customers, and, although a large part about it is profits, the concern is mostly (as far as I know) about the users. Microsoft's biggest fear is wide-spread virus epidemics, so when a critical vulnerability is fully disclosed without prior notice to MSRC, Microsoft goes into an emergency state and everyone gets off of vacation early to come in and help resolve the issue (as was the case with my auto-sp2rc release in December, also called "Paul's Christmas" by MSRC employees). Microsoft knows that security researchers hang out on lists like fd a bugtraq, so what better place to eliminate the common improper disclosing ignorance than to provide clear, concise instructions directly on the security hotspots?

Regards,
Paul
Greyhats Security
http://greyhatsecurity.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050411/833889ee/attachment.html