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: <200504122111.j3CLBQ6a025304@turing-police.cc.vt.edu>
Date: Tue Apr 12 22:11:37 2005
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: How to Report a Security
	VulnerabilitytoMicrosoft 

On Tue, 12 Apr 2005 17:00:46 EDT, mcbain@....com said:

> Also, they do not "patch" they find the root of the problem which adds more time.

This explains why we *never* *ever* see stuff 2 days after Patch Tuesday where
people are reporting "this slight variant still works" because Microsoft always
gets to the *root* of the problem and fixes it *right*, rather than just fixing
the one already-known manifestation....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20050412/5118a134/attachment.bin