lkml.org 
[lkml]   [2013]   [Jul]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [Ksummit-2013-discuss] [ARM ATTEND] catching up on exploit mitigations
From
On Tue, Jul 30, 2013 at 4:15 PM, Dave Jones <davej@redhat.com> wrote:
> 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.

Exactly, and finding those problems tends to be worth the hardware hassle. :)

-Kees

--
Kees Cook
Chrome OS Security


\
 
 \ /
  Last update: 2013-07-31 02:21    [W:0.067 / U:1.796 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site