linux-kernel - Re: [PATCH] objtool: Detect assembly code falling through to INT3 padding

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: <20180518160638.GG17285@pd.tnic>
Date:   Fri, 18 May 2018 18:06:38 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     "H. Peter Anvin" <hpa@...or.com>
Cc:     Ingo Molnar <mingo@...nel.org>,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Alexey Dobriyan <adobriyan@...il.com>,
        Peter Anvin <h.peter.anvin@...el.com>,
        kernel test robot <xiaolong.ye@...el.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Andrew Lutomirski <luto@...nel.org>,
        Brian Gerst <brgerst@...il.com>,
        Denys Vlasenko <dvlasenk@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        tipbuild@...or.com, LKP <lkp@...org>
Subject: Re: [PATCH] objtool: Detect assembly code falling through to INT3
 padding

On Fri, May 18, 2018 at 12:27:15AM -0700, H. Peter Anvin wrote:
> On 05/18/18 00:18, Ingo Molnar wrote:
> > 
> > Ok, this is cool, it addresses the robustness problem that INT3 padding introduced 
> > very nicely.
> > 
> > The concept of built-in kernel tooling working at the machine code level is just 
> > so powerful - we should have added our own KCC compiler 20 years ago.
> > 
> 
> How many times has this been suggested? ;)

Goes to show we still really need it. Imagine the simplifications and
improvements we'll be able to do. Oh myyy....

/me has a wet dream.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.