At Wed, 10 Jan 2007 04:49:03 +0300, Anton Tagunov <[EMAIL PROTECTED]> 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 http://www.eff.org/Infrastructure/trusted_computing/20031001_tc.php 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. Thanks, Marcus _______________________________________________ L4-hurd mailing list [email protected] http://lists.gnu.org/mailman/listinfo/l4-hurd
