linux-kernel - Re: [RFC PATCH] x86/Kconfig: Disable KASLR on debug builds

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231130124909.GEZWiExTP4J1pjNxPq@fat_crate.local>
Date:   Thu, 30 Nov 2023 13:49:09 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] x86/Kconfig: Disable KASLR on debug builds

On Thu, Nov 30, 2023 at 01:08:31PM +0100, Peter Zijlstra wrote:
> Works for me, but I have "nokaslr no_hash_pointers" on all my machines
> by now. It goes right along with "debug ignore_loglevel
> sysrq_always_enabled earlyprintk=serial,ttyS0,115200" :-)

Bah, there's cmdline switches. Lemme add them to all my scripts starting
guests and grub too. Thanks for the hint!

I guess we could still do the Kconfig dependency when we're on new
machines, without the scripts.

Btw, I'm not the only one who's walked right into this one:

config KCOV
        bool "Code coverage for fuzzing"

	...

          If RANDOMIZE_BASE is enabled, PC values will not be stable across
          different machines and across reboots. If you need stable PC values,
          disable RANDOMIZE_BASE.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette