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: <20040211163641.Q1246@thorolf.nat>
From: thorolf at grid.einherjar.de (Thorolf)
Subject: How much longer?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

My presupposition ...

 - US located vendor must have backdoors "by inofficiale rules of
government"...

Isn't it?

Regards,
Rafal Lesniak

Ps. sorry for my poor english.

On Tue, 10 Feb 2004, Geoincidents wrote:

> 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?
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iQCVAwUBQCpNmu2ijGMJcqkLAQLKywQAssNE5DYugWPCaYGQ6qfnXWTKZs1NmsXB
d9PjSSOyWHp/s3tElN6JgCjKIoyU94DE6gde/PqCTgkR2lSGh4eYpGp7AwDLGZi8
yVsuIuOd1FDRFFXpuGih2v2dbHbuFeKCaQL5o6P8SxxQKeKXQm3YzE5bi89td/Lw
p5bUHx7Zjw4=
=7oDj
-----END PGP SIGNATURE-----