From: erik quanstrom <quanstro@labs.coraid.com>
To: corey@bitworthy.net, 9fans@9fans.net
Subject: Re: [9fans] how to lock cpu console
Date: Wed, 1 Sep 2010 15:52:40 -0400 [thread overview]
Message-ID: <a871f53b5e7efc43e3707ab2771b53a7@coraid.com> (raw)
In-Reply-To: <201009011214.12488.corey@bitworthy.net>
> Also, a logical fallacy: Since X could sometimes be used to thwart Y, then
> Y is useless in all cases.
i think the correct statement of the thinking (or
at least my thinking) is
we want to assert X, but
since Y defeats X, we require !Y to assert X.
in something closer to english, the assertion is that
if one requires a secure server, you've got to have physical
security. since there are too many easy ways to circumvent
most known security measures given physical access.
i don't think this assertion has anything to say about
console locking, just that it doesn't solve the stated problem—
execepting, of course, if the data on non-volatile storage is
is encrypted and the key is lost on reboot.
- erik
next prev parent reply other threads:[~2010-09-01 19:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 14:20 baux80
2010-08-31 14:31 ` Robert Raschke
2010-08-31 14:55 ` John Floren
2010-08-31 15:04 ` erik quanstrom
2010-08-31 15:25 ` David Leimbach
2010-08-31 15:25 ` Skip Tavakkolian
2010-08-31 18:18 ` Francisco J Ballesteros
2010-08-31 19:54 ` andrey mirtchovski
2010-08-31 20:45 ` Skip Tavakkolian
2010-09-01 4:21 ` Federico G. Benavento
2010-09-01 4:44 ` John Floren
2010-09-01 15:11 ` erik quanstrom
2010-09-01 16:57 ` Federico G. Benavento
2010-09-01 17:22 ` erik quanstrom
2010-09-01 17:44 ` John Floren
2010-09-01 18:14 ` erik quanstrom
2010-09-01 18:31 ` John Floren
2010-09-01 18:51 ` erik quanstrom
2010-09-01 19:41 ` John Floren
2010-09-01 18:24 ` frank
2010-09-01 17:56 ` Federico G. Benavento
2010-09-01 10:09 ` baux80
2010-09-01 10:09 ` baux80 at gmail.com
2010-09-01 9:56 ` baux80
2010-09-01 9:56 ` baux80 at gmail.com
[not found] ` <E1Oqk2g-0003Ze-1W@gouda.swtch.com>
2010-09-01 19:14 ` Corey
2010-09-01 19:52 ` erik quanstrom [this message]
2010-09-01 20:23 ` Corey
2010-09-01 9:48 ` baux80 at gmail.com
2010-09-01 9:48 ` baux80
2010-08-31 14:20 baux80 at gmail.com
[not found] <E1OqRh3-0005IS-Hi@gouda.swtch.com>
2010-08-31 14:29 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a871f53b5e7efc43e3707ab2771b53a7@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).