Savanna.gnu.org compromised too
Posted Dec 4, 2003 13:44 UTC (Thu) by
RobSeace (subscriber, #4435)
In reply to:
Savanna.gnu.org compromised too by tymiles
Parent article:
Savanna.gnu.org compromised too
Perhaps a little of both? Nothing is ever going to be completely secure,
so all of the people who claimed that Linux (or OpenBSD, or anything else)
is are simply fools... But, I think MOST people were only trying to claim
that Linux was far more secure than Windoze... And, there, I think there
can be no doubt as to the truth of that claim...
But, I personally have always considered that on ANY host running ANY OS,
any unpriviledged local user can gain root, if they really want to, and try
hard enough... I'm not saying local security isn't important, I'm just
saying I always operate under the assumption that if one can run arbitrary
code on the machine, no matter with WHAT priviledges, then they can also
run code as root, if they truly want to... So, that means only allow people
you truly TRUST (including trusting them to keep their home machines secure)
to login to your machine, and then only via secure channels... And, it means
keeping all network services (no matter if they run as root or not) secure...
In my opinion, the REAL problem is NOT a new local root exploit... Big
deal; there are probably several dozen other ways to gain root from a local
user account on most systems... The REAL problem is in anyone untrusted
being able to run arbitrary code (regardless of priviledge level) on a
remote machine... So, instead of focusing all of the effort and attention
on this brk() hole, I'd MUCH rather see it be focused on how the people got
unpriviledged access, in the first place... Apparently, in the Debian case
at least, there was a "sniffed password"... Sniffed where, and how?? From
the user's home system? If so, that user should be beaten, and not let
back in until someone can guarantee the security of their home system from
remote compromises... If sniffed from a compromised server they logged in
to, then it becomes a matter of tracking down how THAT server was
compromised... But, in the end, it'll likely come down to some user whose
home system was setup insecurely, and remotely compromised... And, THAT is
the real, basic problem... A chain is only as strong as its weakest link...
Of course, we should continue to fix local holes like this, but I think
putting as much focus on them as has been done is WAY out of proportion,
and completely missing where the real focus should go: finding the weak
link, and fixing IT... Because, I can assure you, some OTHER local root
compromise will be found someday (if there aren't already several others
already known)... I just think it's inevitable... It's far harder to
protect against a legit local user than it is to protect against an unknown
remote intruder... And, really, if we cut off all possible remote
intrusions (whether they be root compromises or merely unpriviledged ones),
then the local ones become nearly irrelevent... (Except for those few
people who want to run servers that give random untrusted people login
access on their systems, anyway... And, I think those people are just
rather insane, anyway... But, you know, once we've completely nailed down
all remote compromises, THEN we can start focusing on the local ones much
more intently, and help such crazy people... ;-))
(
Log in to post comments)