[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 14 Feb 2017 17:54:05 +0000
From: Mark Rutland <mark.rutland@....com>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
CC: <linux-arm-kernel@...ts.infradead.org>, <catalin.marinas@....com>,
<will.deacon@....com>, <labbott@...oraproject.org>,
<kvmarm@...ts.cs.columbia.edu>, <marc.zyngier@....com>,
<andre.przywara@....com>, <Suzuki.Poulose@....com>, <james.morse@....com>,
<keescook@...omium.org>, <kernel-hardening@...ts.openwall.com>, <nd@....com>
Subject: Re: [PATCH v2 4/5] arm64: mmu: map .text as read-only from the outset
On Tue, Feb 14, 2017 at 05:49:19PM +0000, Ard Biesheuvel wrote:
>
> > On 14 Feb 2017, at 17:40, Mark Rutland <mark.rutland@....com> wrote:
> >
> >> On Tue, Feb 14, 2017 at 04:15:11PM +0000, Ard Biesheuvel wrote:
> >> Having trivial 'off' switches for security features makes me feel
> >> uneasy (although this is orthogonal to this patch)
> >
> > From my PoV, external debuggers are the sole reason to allow rodata=off
> > for arm64, and we already allow rodata=off.
> >
> >
>
> Indeed. If that is how it works currently, we shouldn't interfere with
> it. If we ever get anywhere with the lockdown patches, we should
> blacklist this parameter (or rather, not whitelist it, since
> blacklisting kernel params to enforce security is infeasible imo)
Agreed on all counts!
Mark.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
