full-disclosure - Microsoft confirms source code leak

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: <200402132355.i1DNt7Yb008857@turing-police.cc.vt.edu>
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks@...edu)
Subject: Microsoft confirms source code leak 

On Fri, 13 Feb 2004 14:01:45 EST, "Bernie, CTA" <cta@...in.net>  said:

> Microsoft knew or should of known that their Win OS was going to 
> be deployed in a solution that was designed to ensure the 
> security (integrity, confidentiality, accessibility) of people, 
> premises, critical infrastructure, systems, resources or data 
> and knew or should have known that their Win OS had 
> flaws/vulnerabilities which could be exploited to threaten such 
> security and failed to disclose such flaws/vulnerabilities to 
> the buyer.

They disclosed and disclaimed it when you clicked OK on the EULA.

Go poke around in C:\win32, find eula.txt, and start reading. There's
probably even a disclaimer regarding nuclear power plants in there.

Honestly.
-------------- 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/20040213/ddbe4d5c/attachment.bin