lkml.org 
[lkml]   [1999]   [Jan]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.0 SECURITY
Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> "stuff"? Like corrupting the coredump? Doesn't seem to be the height of
> problems. I think at worst you could corrupt the content of the file, but
> you can't make it start writing to the wrong place.

David S. Miller <davem@dm.cobaltmicro.com> wrote:
> I'm just being anal here... you're probably right.

Only if it's not a good idea to do debugging in a multi-user
environment.

gdb makes it quite simple to call target program functions from inside a
debugging session. Imagine that someone works out how to insert a trojan
inside a core file (I dunno -- by mucking up a jump table or some such).

Even worse if someone has a reason to be debugging as root...

So, maybe it's a low risk, but it's not no risk.

--
Raul

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.072 / U:0.880 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site