full-disclosure - How to Report a Security VulnerabilitytoMicrosoft

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: <20050412211417.GD5168@sivokote.iziade.m$>
Date: Tue Apr 12 22:14:26 2005
From: guninski at guninski.com (Georgi Guninski)
Subject: How to Report a Security
	VulnerabilitytoMicrosoft

On Tue, Apr 12, 2005 at 05:00:46PM -0400, mcbain@....com wrote:
>  
> The reason for this (from redmond) is they cannot break computers that are out there. There tolerance has to be even below one percent ,and even that is too much and finally conceded with them on their points.  Also, they do not "patch" they find the root of the problem which adds more time.  So you should be seeing less workarounds of microsoft patches. 
>

they are breaking computers out there all the time.

so they know their code is a mess, but want the 0day to be private to them
for 5 months so they can profit more. a nice plan.

i thought bill's trusthy computing intiative cured the "root of the
problem" or not? the m$ whores patching holes for several billions worth and
*more* exploits left?

-- 
where do you want bill gates to go today?