full-disclosure - Windows 2000 Source Leak Verified. Get ready for the havoc.

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: <402E5262.60809@onryou.com>
From: lists2 at onryou.com (Cael Abal)
Subject: Windows 2000 Source Leak Verified. Get ready
 for the havoc.

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

| are they actually .asm, .c files and .h files in them ?
|
| or whatever lang was used to code windows?

As opposed to literally being 'blueprints' as reported by virtually
every major news source?

That's a bit of a pet peeve of mine -- writers who don't quite
understand what they're writing about and/or feel the need to make (bad)
analogies in order to get an idea across.

This bothers me because I can only consistently call them on it when
they're discussing tech-related topics...  I realize they're likely
doing exactly the same thing when discussing things I'm not
knowledgeable about.

Cael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)

iD8DBQFALlJiR2vQ2HfQHfsRArpTAJ0dZEFb1F6nKnfZRVvRXstBxYdv7wCgtttm
o1tOC1/HSwqVZTfr0WBJiPA=
=TdZJ
-----END PGP SIGNATURE-----