full-disclosure - How to Report a Security Vulnerability to M icrosoft

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

Message-ID: <7EF7F2227EFFC445B5B244495CDC9D5101CE9C00@hhpech01.healthaxis.dom>
Date: Thu Apr 28 22:17:07 2005
From: CCapps at healthaxis.com (Capps, Chuck)
Subject: How to Report a Security Vulnerability to M
	icrosoft

Ignore him.  Guninski is the biggest Microsoft whiner I have ever had the
displeasure of having to listen to.  Spend a few weeks on this list and you
will be writing a special rule for him also.

Chuck



-----Original Message-----
From: Tatercrispies [mailto:tatercrispies@...il.com] 
Sent: Thursday, April 28, 2005 4:13 PM
To: full-disclosure@...ts.grok.org.uk
Subject: Re: [Full-disclosure] How to Report a Security Vulnerability to
Microsoft

What do you want confirmation about? It's not a big secret when the
big-assed dialog box pops up and asks if you'd like to submit crash
data to Microsoft's servers. (sorry, M$'$ $ervers)

https://winqual.microsoft.com/help/wer_help/dev.aspx


On 4/28/05, Georgi Guninski <guninski@...inski.com> wrote:
> i would like m$ to officially confirm they are collecting crashes and
> confidential information from third parties warez.
> 
> because i am sure my humble application c:\fsckb11.EXE does not send crash
> reports to m$ in the cases when it crashes.
> 
>
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/