From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: "Ortwin Glück" <odi@odi.ch>, "Drew DeVault" <sir@cmpwn.com>,
"Richard Weinberger" <richard@nod.at>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Failover root devices
Date: Fri, 18 Sep 2015 11:36:09 -0400 [thread overview]
Message-ID: <55FC2F69.9030609@gmail.com> (raw)
In-Reply-To: <55FC2815.7070806@odi.ch>
[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]
On 2015-09-18 11:04, Ortwin Glück wrote:
>> If you have physical access then the machine is yours to do with as
>> you please.
>
> Thinking of ATMs or voting machines that is a bold statement :-)
Many voting machines already have known ACE exploits already (I
distinctly remember a while back some CS students demonstrated a
'modern' voting machine playing PAC-Man without modifying any of the
hardware at all), and those that have network access or other accessible
peripheral connections are inherently insecure, period.
And most ATM's (at least in the US) run Windows (_shivers_) XP or
eCommStation (the current commercial version of OS/2 (yes it still lives
on), neither of which is particularly secure even when it comes to
remote access to the system, and even then, the kind of access you need
would involve3 directly tampering with the system.
Irrespective of that, neither one should be configured to work like
that. The intent is for custom setups primarily, if some company
decides to use this in an insecure way, that's their problem, not ours
(it's really easy to use a wide number of kernel features in ways that
compromise security, that doesn't mean we should just rip those out).
>
> Thinking of mobile phones it depends on your jurisdiction.
This isn't a legal ruling, it's a simple statement of fact, if someone
has physical access to a system, they effectively have root access,
period. While this is not probably what the above comment was directly
referring to, it is an established fact.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-09-18 15:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 11:40 Failover root devices Ortwin Glück
2015-09-17 11:49 ` Drew DeVault
2015-09-17 17:47 ` Richard Weinberger
2015-09-17 17:49 ` Drew DeVault
2015-09-17 17:52 ` Richard Weinberger
2015-09-17 18:05 ` Drew DeVault
2015-09-17 18:17 ` Richard Weinberger
2015-09-17 18:18 ` Drew DeVault
2015-09-17 18:19 ` Richard Weinberger
2015-09-17 18:21 ` Drew DeVault
2015-09-17 18:23 ` Richard Weinberger
2015-09-17 18:28 ` Drew DeVault
2015-09-18 14:59 ` Ortwin Glück
2015-09-18 15:00 ` Drew DeVault
2015-09-18 15:04 ` Ortwin Glück
2015-09-18 15:36 ` Austin S Hemmelgarn [this message]
2015-09-17 18:27 ` Harald Hoyer
2015-09-17 18:29 ` Drew DeVault
2015-09-17 18:33 ` Richard Weinberger
2015-09-17 18:35 ` Drew DeVault
2015-09-17 18:42 ` Richard Weinberger
2015-09-17 18:29 ` Richard Weinberger
2015-09-17 18:37 ` Austin S Hemmelgarn
2015-09-17 18:40 ` Richard Weinberger
2015-09-18 14:40 ` Austin S Hemmelgarn
-- strict thread matches above, loose matches on Subject: below --
2015-09-17 0:16 Drew DeVault
2015-09-17 16:02 ` Austin S Hemmelgarn
2015-09-17 17:30 ` Drew DeVault
2015-09-18 14:34 ` Austin S Hemmelgarn
2015-09-18 14:43 ` Drew DeVault
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=55FC2F69.9030609@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=odi@odi.ch \
--cc=richard@nod.at \
--cc=sir@cmpwn.com \
/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