full-disclosure - M$ - so what should they do?

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: <40D7119A.3000600@mistrealm.com>
From: mbs at mistrealm.com (Michael Schaefer)
Subject: M$ - so what should they do?

Well, lets see, moving away from the Registry (single point of failure) 
would be a good step.

Separating the operating system from programs would be great, I don't 
like the fact that everything and it's brother thinks it can or should 
dump files into the system directory.

What else is flawed? What other changes should be made?

William Warren wrote:

> redeisgn their products..the basic windows design is flawed and needs 
> reworking for one thing..:)
>
> Michael Schaefer wrote:
>
>> What would you suggest Microsoft do to improve ?
>