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

Message-ID: <20050413160957.GA14243@linux.unixwiz.net>
Date: Wed Apr 13 17:10:05 2005
From: steve at unixwiz.net (Steve Friedl)
Subject: How to Report a Security Vulnerability to
	Microsoft

On Wed, Apr 13, 2005 at 06:42:22PM +0300, Georgi Guninski wrote:
> m$ users have deal with m$.
> the m$ eula clearly explains to users that if users get fucked because of m$
> warez m$ are not responsible.
> 
> you are proposing a 3rd party to save m$ users?

I'm proposing that security researchers act like professionals who care
about other people, not arrogant headline-seekers who only care about
fscking a company they don't like.

It's OK to hate Microsoft for a whole host of reasons ("their lawyers"
do it for me), but when you're OK with screwing their *users*, that says
a lot more about you than it does about Microsoft.

And you don't lose your technical creds by doing it responsibly.

Steve

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