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

What would you suggest Microsoft do to improve ?

Georgi Guninski wrote:

>i am replying to the whole m$ thread, nothing personal.
>
>m$ are so bad, so it is really difficult for them to get any worse, but this
>does not mean they are really getting better.
>
>they crossed the badness point of no return() long time ago.
>
>georgi
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.netsys.com/full-disclosure-charter.html
>  
>