From: davej@redhat.com (Dave Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2013-discuss] [ARM ATTEND] catching up on exploit mitigations
Date: Tue, 30 Jul 2013 19:15:33 -0400 [thread overview]
Message-ID: <20130730231533.GA26824@redhat.com> (raw)
In-Reply-To: <20130730231120.GC30725@blackmetal.musicnaut.iki.fi>
On Wed, Jul 31, 2013 at 02:11:20AM +0300, Aaro Koskinen wrote:
> Hi,
>
> On Tue, Jul 30, 2013 at 06:14:35PM -0400, Dave Jones wrote:
> > On Tue, Jul 30, 2013 at 12:05:40PM -0700, Kees Cook wrote:
> > > - fuzzing (is anyone running trinity or similar on the ARM tree?)
> >
> > Someone was kind enough to send me an arm chromebook, so I tried this just
> > last week (albeit, on the 3.4 kernel it shipped with). The results make
> > me think the answer is a resounding 'no'.
>
> Shouldn't you run trinity only under QEMU or similar virtual
> environment? Don't know about chromebook, but on some of my ARM boards
> a misbehaving kernel could at least in theory brick the board...
I like to live dangerously. Don't imitate everything you see on TV,
or read about on lkml.
More seriously, that's true if you're running trinity as root, which
yes, I usually advise people only do in qemu etc.
If you're running it as a regular user and you can brick the board,
you might have bigger problems.
Dave
next prev parent reply other threads:[~2013-07-30 23:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 19:05 [ARM ATTEND] catching up on exploit mitigations Kees Cook
2013-07-30 22:14 ` [Ksummit-2013-discuss] " Dave Jones
2013-07-30 22:28 ` H. Peter Anvin
2013-07-31 13:55 ` Jason Cooper
2013-07-30 23:11 ` Aaro Koskinen
2013-07-30 23:15 ` Dave Jones [this message]
2013-07-30 23:33 ` Kees Cook
2013-07-31 0:01 ` H. Peter Anvin
2013-07-30 23:58 ` Aaro Koskinen
2013-07-31 0:04 ` Dave Jones
2013-07-31 9:40 ` Russell King - ARM Linux
2013-07-31 14:24 ` Dave Jones
2013-08-01 2:47 ` Olof Johansson
2013-08-01 2:59 ` Dave Jones
2013-08-01 16:02 ` Vince Weaver
2013-08-21 15:26 ` Russell King - ARM Linux
2013-08-21 15:43 ` Dave Jones
2013-08-21 15:56 ` Russell King - ARM Linux
2013-08-01 9:13 ` Dan Carpenter
2013-08-01 19:05 ` Dave Jones
2013-08-01 19:16 ` Dan Carpenter
2013-08-01 19:26 ` Julia Lawall
2013-08-03 0:03 ` Russell King - ARM Linux
2013-08-06 21:44 ` Kees Cook
2013-08-13 4:51 ` Laura Abbott
2013-08-26 19:56 ` Mark Brown
2013-08-27 2:09 ` Laura Abbott
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=20130730231533.GA26824@redhat.com \
--to=davej@redhat.com \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).