From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Raid 0 setup doubt.
Date: Tue, 29 Mar 2016 01:46:25 +0000 (UTC) [thread overview]
Message-ID: <pan$5eff2$9df187d8$1f5c7833$dba90a9e@cox.net> (raw)
In-Reply-To: 56F9252F.90704@gmail.com
Austin S. Hemmelgarn posted on Mon, 28 Mar 2016 08:35:59 -0400 as
excerpted:
> The other caveat that nobody seems to mention outside of specific cases
> is that using suspend to disks exposes you to direct attack by anyone
> with the ability to either physically access the system, or boot an
> alternative OS on it. This is however not a Linux specific issue
> (although Windows and OS X do a much better job of validating the
> hibernation image than Linux does before resuming from it, so it's not
> as easy to trick them into loading arbitrary data).
I believe that within the kernel community, it's generally accepted that
physical access is to be considered effectively full root access,
because there's simply too many routes to get root if you have physical
access to practically control them all. I've certainly read that.
Which is what encryption is all about, including encrypted / (via initr*)
if you're paranoid enough, as that's considered the only effective way to
thwart physical-access == root-access.
And even that has some pretty big assumptions if physical access is
available, including that no hardware keyloggers or the like are planted,
as that would let an attacker simply log the password or other access key
used. One would have to for instance use a wired keyboard that they kept
on their person (or inspect the keyboard, including taking it apart to
check for loggers), and at minimum visually inspect its connection to the
computer, including having a look inside the case, to be sure, before
entering their password. Or store the access key on a thumbdrive kept on
the person, etc, and still inspect the computer left behind for listening/
logging devices...
In practice it's generally simpler to just control physical access
entirely, to whatever degree (onsite video security systems with tamper-
evident timestamping... kept in a vault, missile silo, etc) matches the
extant paranoia level.
Tho hosting the swap, and therefore hibernation data, on an encrypted
device that's setup by the initr* is certainly possible, if it's
considered worth the trouble. Obviously that's going to require jumping
thru many of the same hoops that (as mentioned upthread) splitting the
hibernate image between devices will require, as it generally uses the
same underlying initr*-based mechanisms. I'd certainly imagine the
Snowden's of the world will be doing that sort of thing, among the
multitude of security options they must take.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2016-03-29 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 10:35 Raid 0 setup doubt Jose Otero
2016-03-28 0:56 ` Duncan
2016-03-28 5:26 ` James Johnston
2016-03-28 8:51 ` Duncan
2016-03-28 12:35 ` Austin S. Hemmelgarn
2016-03-29 1:46 ` Duncan [this message]
2016-03-29 2:10 ` Chris Murphy
2016-03-28 20:30 ` Jose Otero
2016-03-29 4:14 ` Duncan
2016-03-28 2:42 ` Chris Murphy
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='pan$5eff2$9df187d8$1f5c7833$dba90a9e@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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).