linux-kernel - Re: [git pull] coredump infoleak fix

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAHk-=whsZ_en9wEwk+VuAGMXACcSDCYhMD-GmQER0snpp9S6yg@mail.gmail.com>
Date:   Thu, 28 May 2020 12:19:32 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Al Viro <viro@...iv.linux.org.uk>
Cc:     Ingo Molnar <mingo@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [git pull] coredump infoleak fix

On Thu, May 28, 2020 at 12:17 PM Al Viro <viro@...iv.linux.org.uk> wrote:
>
> Might make sense to change the summary of that pull request to something
> like
>         make sure we don't forget to report the xstate components that happen
> to be in init state - both for coredump and for PTRACE_GETREGSET

Note that this has nothing to do with x86 per se.

It's more about ->getregs() being a horrid interface, and being easy
to get wrong in general. The fact that xstate is complex is just one
such trigger.

              Linus