full-disclosure - CyberInsecurity: The cost of Monopoly

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

Message-ID: <1A595BB1C1CEAF4CB673755028BBD7CF02EB1D74@himl06.hickam.pacaf.ds.af.mil>
From: Sung.Choe at hickam.af.mil (Choe.Sung Cont. PACAF CSS/SCHP)
Subject: CyberInsecurity: The cost of Monopoly

> I think it might be more of a problem for Microsoft itself. How can you
fix
> the problems and still try to sell new versions to the public?

Micro$oft's business model is not selling software that is (relatively)
bug-free.  Rather, they like bringing products to market ASAP, regardless of
the security risks that these "products" pose to the consumer.  If they were
ever to release software that was free of such "problems", would they still
be able to sell new versions to the public?  I would think not...

V/r,
Sung J. Choe
PACAF CSS/SCHP, PACAF NOSC
Information Assurance Analyst
DSN: 315-449-4317, Comm: 808-449-4317

-----Original Message-----
From: Peter Busser [mailto:peter@...steddebian.org] 
Sent: Saturday, September 27, 2003 3:53 AM
To: full-disclosure@...ts.netsys.com
Subject: Re: [Full-Disclosure] CyberInsecurity: The cost of Monopoly