Full Disclosure mailing list archives
Re: Why Vulnerability Databases can't do everything
From: "J.A. Terranson" <measl () mfn org>
Date: Sat, 16 Jul 2005 13:05:50 -0500 (CDT)
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 () mfn 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) _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- Why Vulnerability Databases can't do everything Steven M. Christey (Jul 15)
- Re: Why Vulnerability Databases can't do everything Georgi Guninski (Jul 16)
- Re: Why Vulnerability Databases can't do everything ph0enix (Jul 16)
- Re: Why Vulnerability Databases can't do everything Georgi Guninski (Jul 16)
- RE: Why Vulnerability Databases can't do everything aaron_kempf (Jul 16)
- <Possible follow-ups>
- Re: Why Vulnerability Databases can't do everything Jason Coombs (Jul 16)
- Re: Why Vulnerability Databases can't do everything J.A. Terranson (Jul 16)
- Re: Why Vulnerability Databases can't do everything Georgi Guninski (Jul 16)