[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Back door design

From: Marcus Brinkmann
Subject: Re: Back door design
Date: Wed, 10 Jan 2007 03:19:36 +0100
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 Emacs/21.4 (i486-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Wed, 10 Jan 2007 04:49:03 +0300,
Anton Tagunov <address@hidden> wrote:
> I think I've designed it :)) Please judge me.
> 1. Administration
> OS runs in one of two modes - opaque (default) and debug.
> Opaque mode == no application has been designated as "Debugger".
> Debug mode  == there is at least one application designated as "Debugger".
> OS Admin GUI has a section used to
> * designate any application as "Debugger"
> * designate any application as exempt from debugging (irreversible)
> * disable debugging completely (irreversible)
> To enter this section Admin has to perform a sufficiently arcane procedure 
> [1].

To put this into the context of "trusted computing", let me repeat a
remark I just made in another reply.  The ability to "debug" (or
cheat) transparently for remote attestation was also made here:

Trusted Computing: Promise and Risk By Seth Schoen
You may want to compare your proposal with "Owner Override" as
described there.  The ability to mark some processes as exempt is an
interesting addition.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]