full-disclosure - How much longer?

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: <017601c3f045$98a0f1c0$231a90d8@NTAUTHORITY>
From: geoincidents at getinfo.org (Geoincidents)
Subject: How much longer?

This is a serious security issue imo

http://www.eeye.com/html/Research/Upcoming/index.html

I just saw this page for the first time today and I find this totally
unacceptable behavior from a vendor. Where is the priority for root level
exploits? Are you people comfortable knowing that a vendor has and *always
will have* full backdoor access to all your Windows systems as long as we
allow lag times like these?

So the question is, how much longer is the security community going to
tollerate this industry supported backdoor CRAP before getting back to full
public disclosure with a 2 week warning for the vendor? Obviously force is
required when dealing with slackers.

Geo. (why haven't the news folks picked up on this for what it is, known
backdoors to all Windows systems)

Note to Marc from eeye, correct me if I'm wrong, most of these are backdoors
right?