public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] linux: Give CONFIG_RANDOMIZE_BASE on aarch64 another try
Date: Tue, 12 Jul 2022 09:45:29 +0000	[thread overview]
Message-ID: <ca8a2731-582d-90e5-5b65-418b243599e4@ipfire.org> (raw)
In-Reply-To: <DB7BFB1C-C819-46CE-AF39-3DFBD0DFE55F@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2855 bytes --]

Hello Michael,

> Shouldn’t this rather be called an RFC before we propose this as a patch?

indeed, this should have had the RFC flag. Apologies.

> AFAIK this causes problems on some single board computers - so those people who run them would need to give feedback whether this is causing them any regressions.

No, last time (in 2020) we tried this, things would not even compile. So no ARM64
users were harmed, though I agree, we definitely need robust testing feedback on
such a change.

Thanks, and best regards,
Peter Müller

> 
> Best,
> -Michael
> 
>> On 11 Jul 2022, at 17:07, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Quoted from https://capsule8.com/blog/kernel-configuration-glossary/:
>>
>>> Significance: Critical
>>>
>>> In support of Kernel Address Space Layout Randomization (KASLR) this randomizes
>>> the physical address at which the kernel image is decompressed and the virtual
>>> address where the kernel image is mapped as a security feature that deters
>>> exploit attempts relying on knowledge of the location of kernel code internals.
>>
>> We tried to enable this back in 2020, and failed. Since then, things
>> may have been improved, so let's give this low-hanging fruit another
>> try.
>>
>> Fixes: #12363
>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>> ---
>> config/kernel/kernel.config.aarch64-ipfire | 2 +-
>> config/rootfiles/common/aarch64/linux      | 1 +
>> 2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/config/kernel/kernel.config.aarch64-ipfire b/config/kernel/kernel.config.aarch64-ipfire
>> index 469884b20..9232335ff 100644
>> --- a/config/kernel/kernel.config.aarch64-ipfire
>> +++ b/config/kernel/kernel.config.aarch64-ipfire
>> @@ -471,7 +471,7 @@ CONFIG_ARM64_SVE=y
>> CONFIG_ARM64_MODULE_PLTS=y
>> # CONFIG_ARM64_PSEUDO_NMI is not set
>> CONFIG_RELOCATABLE=y
>> -# CONFIG_RANDOMIZE_BASE is not set
>> +CONFIG_RANDOMIZE_BASE=y
>> CONFIG_CC_HAVE_STACKPROTECTOR_SYSREG=y
>> CONFIG_STACKPROTECTOR_PER_TASK=y
>> # end of Kernel Features
>> diff --git a/config/rootfiles/common/aarch64/linux b/config/rootfiles/common/aarch64/linux
>> index 906fde0c3..af96753fc 100644
>> --- a/config/rootfiles/common/aarch64/linux
>> +++ b/config/rootfiles/common/aarch64/linux
>> @@ -9427,6 +9427,7 @@ etc/modprobe.d/ipv6.conf
>> #lib/modules/KVER-ipfire/build/include/config/RAID6_PQ
>> #lib/modules/KVER-ipfire/build/include/config/RAID6_PQ_BENCHMARK
>> #lib/modules/KVER-ipfire/build/include/config/RAID_ATTRS
>> +#lib/modules/KVER-ipfire/build/include/config/RANDOMIZE_BASE
>> #lib/modules/KVER-ipfire/build/include/config/RANDOMIZE_KSTACK_OFFSET_DEFAULT
>> #lib/modules/KVER-ipfire/build/include/config/RAS
>> #lib/modules/KVER-ipfire/build/include/config/RASPBERRYPI_FIRMWARE
>> -- 
>> 2.35.3
> 

      reply	other threads:[~2022-07-12  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 15:07 Peter Müller
2022-07-11 16:58 ` Michael Tremer
2022-07-12  9:45   ` Peter Müller [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=ca8a2731-582d-90e5-5b65-418b243599e4@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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