Messages in this thread | | | Date | Thu, 26 Jul 2012 18:07:09 +0100 | From | Alan Cox <> | Subject | Re: [PATCH 6/7] kdb: Mark safe commands as KDB_SAFE and KDB_SAFE_NO_ARGS |
| |
> The following commands were marked as "safe": > > Clear Breakpoint > Enable Breakpoint > Disable Breakpoint > Display exception frame > Stack traceback
This is sufficient to steal cryptographic keys in many environments. In fact you merely need two or three breakpoints and to log the order they are hit through the crypto computation.
> Display stack for process
Exposes all sorts of user data unless you mean just the call trace, in which case it's still quite useful.
> Display stack all processes
Ditto
> Send a signal to a process
Like say sending SIGSTOP to security monitoring threads or the battery manager on locked devices that rely on software battery management ?
It's an interesting idea but you need almost nothing to extract keys from a system or to subvert it.
Alan
| |