full-disclosure - RE: [ISN] How To Save The Internet

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

Message-ID: <08D2E56ED9BBDF4E8C59B9E7419A312B03530978@DC201MXC02VA.bcbsfl.com>
From: Tom.Marchand at bcbsfl.com (Marchand, Tom)
Subject: RE: [ISN] How To Save The Internet

Plus, the same code could possibly be considered legitimate for one owner and non-legitimate for another.

-----Original Message-----
From:	David Gillett [mailto:gillettdavid@...a.edu]
Sent:	Tue 3/22/2005 11:45 AM
To:	jasonc@...ence.org; jericho@...rition.org
Cc:	isn@....org; sberinato@....com; full-disclosure@...ts.grok.org.uk; bugtraq@...urityfocus.com
Subject:	RE: [ISN] How To Save The Internet

Jason Coombs [mailto:jasonc@...ence.org] writes:

<snip>
> ... the core problem with computer 
> security is that our CPUs make no effort to restrict the execution of 
> machine code to that very small subset of all possible machine code 
> which constitutes the code that the owner of the CPU desires 
> it to run.

<snip> 

> If anyone really cared about solving this core security problem with 
> computing today, it would be solved in just a few months. 

  Just one of the myriad of security issues that we're grappling with 
are the various rights of the owner of the CPU, the *operator* of the
CPU, and the owner of the *data*, each of whom may have a more or less
legitimate say in what code actually gets executed.  Far too many folks 
have already "solved" this problem incorrectly for me to believe that 
the "just a few months" solution you envisage will actually be correct.

David Gillett

Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc.  The information contained in this document may be confidential and intended solely for the use of the individual or entity to whom it is addressed.  This document may contain material that is privileged or protected from disclosure under applicable law.  If you are not the intended recipient or the individual responsible for delivering to the intended recipient, please (1) be advised that any use, dissemination, forwarding, or copying of this document IS STRICTLY PROHIBITED; and (2) notify sender immediately by telephone and destroy the document. THANK YOU.