full-disclosure - Why Vulnerability Databases can't do everything

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] [day] [month] [year] [list]

Message-ID: <20050716130356.W17410@ubzr.zsa.bet>
Date: Sat Jul 16 19:06:06 2005
From: measl at mfn.org (J.A. Terranson)
Subject: Why Vulnerability Databases can't do everything

On Sat, 16 Jul 2005, Jason Coombs wrote:

> 3) Stop buffering runtime I/O within the same physical memory as machine
> code.

This should have been #1 - and it is something I have been bitching about
since the BIRTH of MPUs in the mid '70s. (yeah, I'm an old mainframe guy,
so I saw the problem.  just like everyone else did.)

90+ percent of our current woes can be laid at the doorstep of this single
fuck up.

-- 
Yours,

J.A. Terranson
sysadmin@....org
0xBD4A95BF

"If I want to gamble, I'll continue to have unprotected
sex with my 14 year old first cousin."

   (T-Shirt Hell Advertisement)