I really doubt that you know the security implications of all the software you run on your system(s), no matter what you say. That's the entire point behind people finding vulnerabilities - it means that there are security implications that no one else knew about (or at least *published*:).
The only way to know the security implications of the software you run is to read the entire source code base (including libraries) and grok it fully, including all interactions, possible program flows, etc. I'm sure by your comment that you of course have done this, but I don't know many others who actually have that kind of time on their hands.
By the way, when are you going to publish all of the vulnerabilities in all those programs that you are using that no one else besides you has found yet?
The truly secure system is one that is off, can't be turned on or accessed in any way.
Slashdot Mirror
I really doubt that you know the security implications of all the software you run on your system(s), no matter what you say. That's the entire point behind people finding vulnerabilities - it means that there are security implications that no one else knew about (or at least *published* :).
The only way to know the security implications of the software you run is to read the entire source code base (including libraries) and grok it fully, including all interactions, possible program flows, etc. I'm sure by your comment that you of course have done this, but I don't know many others who actually have that kind of time on their hands.
By the way, when are you going to publish all of the vulnerabilities in all those programs that you are using that no one else besides you has found yet?
The truly secure system is one that is off, can't be turned on or accessed in any way.
From the article:
Linux plans face upheaval
By Mark Street [03-09-2002]
Hello? This artice is six months old, and it's news?