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  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]
Date:   Mon, 3 Jan 2022 17:59:27 +0100
From:   Borislav Petkov <>
To:     Alexander Lobakin <>
        Jesse Brandeburg <>,
        Kristen Carlson Accardi <>,
        Kees Cook <>,
        Miklos Szeredi <>,
        Ard Biesheuvel <>,
        Tony Luck <>,
        Bruce Schlobohm <>,
        Jessica Yu <>,
        kernel test robot <>,
        Miroslav Benes <>,
        Evgenii Shatokhin <>,
        Jonathan Corbet <>,
        Masahiro Yamada <>,
        Michal Marek <>,
        Nick Desaulniers <>,
        Herbert Xu <>,
        "David S. Miller" <>,
        Thomas Gleixner <>,
        Will Deacon <>, Ingo Molnar <>,
        Dave Hansen <>,
        "H. Peter Anvin" <>,
        Andy Lutomirski <>,
        Peter Zijlstra <>,
        Arnd Bergmann <>,
        Josh Poimboeuf <>,
        Nathan Chancellor <>,
        Masami Hiramatsu <>,
        Marios Pomonis <>,
        Sami Tolvanen <>,
        "H.J. Lu" <>, Nicolas Pitre <>,,,,,
Subject: Re: [PATCH v9 03/15] kallsyms: Hide layout

On Mon, Jan 03, 2022 at 04:40:23PM +0100, Alexander Lobakin wrote:
> "kallsyms: randomize /proc/kallsyms output order"?


> It displays zeros for non-roots, but the symbols are still sorted by
> their addresses. As a result, if you leak one address, you could
> determine some others.

Because if an attacker has the corresponding vmlinux, he has the offsets
too so, game over?

> This is especially critical with FG-KASLR as its text layout is
> random each time and sorted /proc/kallsyms would make the entire
> feature useless.

Do you notice how exactly this needs to absolutely be in the commit
message? Instead of that "this patch" bla which is more or less obvious.

IOW, always talk about *why* you're doing a change.

> I either have some problems with checkpatch + codespell, or they
> missed all that typos you're noticing. Thanks, and apologies =\

No worries, and thank python's enchant module which I use to spellcheck

So lemme look at the actual patch then :)



Powered by blists - more mailing lists