From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Spectre mitigation doesn't seem to work at all?!
Date: Tue, 5 Jun 2018 07:53:24 +0200 [thread overview]
Message-ID: <55e879f4-57c1-dc55-74ba-b1845cd5ded5@01019freenet.de> (raw)
In-Reply-To: <20180604151251.1fb34793@alans-desktop>
On 06/04/2018 at 04:12 PM Alan Cox wrote:
>> A malicious program most probably won't care about that. Therefore, my
>> next question is: which memory regions can be exploited by a malicious
>> program? The complete physical memory or only the memory provided to the
>> malicious program? Should be the latter if this approach should have any
>> impact.
>
> Spectre is not about memory regions. It's about speculative execution
> leaving measurable footprints. What footprints you leave depend upon what
> code you are executing. Thus the question becomes 'what can the target
> access'.
>
> In order to attack something you need both a way to influence the code
> concerned and a way to measure it. In addition it needs to have some
> secret you want.
>
> In practice that usually means something on the same system with its own
> memory space/privilege level. The usual cases then are user<->kernel and
> managed application<->runtime.
Would this be a practical test case: Gather keys and passwords used by a
ssh login by running a malicious program in parallel to sshd as another
ordinary user w/o root access.
Thanks,
Andreas
prev parent reply other threads:[~2018-06-05 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 12:19 Andreas Hartmann
2018-06-04 7:43 ` Andreas Hartmann
2018-06-04 21:25 ` Thomas Gleixner
2018-06-04 8:15 ` Peter Zijlstra
2018-06-04 8:50 ` Andreas Hartmann
2018-06-04 9:15 ` Peter Zijlstra
2018-06-04 9:19 ` Mark Rutland
2018-06-04 10:00 ` Andreas Hartmann
2018-06-04 14:12 ` Alan Cox
2018-06-05 5:53 ` Andreas Hartmann [this message]
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=55e879f4-57c1-dc55-74ba-b1845cd5ded5@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®