Kernel core dumps (was Re: out of swap space??)

[david.r.connet]

In article <3909 at d75.UUCP> marc at 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.