Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!att!cbnewsc!dcon
From: dcon@cbnewsc.att.com (david.r.connet)
Newsgroups: comp.unix.sysv386
Subject: Re: Kernel core dumps (was Re: out of swap space??)
Keywords: forced panic
Message-ID: <1991May16.144419.7771@cbnewsc.att.com>
Date: 16 May 91 14:44:19 GMT
References: <1991May13.162909.20686@turnkey.tcc.com> <1991May13.204435.3138@cbnewsc.att.com> <3909@d75.UUCP>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 15

In article <3909@d75.UUCP> marc@ekhomeni.austin.ibm.com (Marc Wiz) writes:
>> I only played with it briefly, but it looked like the debugger could be
>> a security hole.  You could bring up a debugger session without being
>> logged on, and probably poke a 0 into the appropriate place in your
>> uarea...
>Yes that is true that you can poke a 0 into the appropriate place.
>However IMHO one of the biggest problems with the debugger was that you
>only had addressability to the current process.
>
>If you wanted to look around in another process' address space you were
>in for an interesting time.  The debugger didn't have that capability.
>

With AT&Ts debugger, you can basically do anything you want to the system.
The only security you have is physical, i/o is done with the console.