linux-kernel - Re: PKU usage improvements for threads

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: <20220903001648.17171-1-yangff1@gmail.com>
Date:   Fri,  2 Sep 2022 19:16:48 -0500
From:   Fangfei Yang <yangff1@...il.com>
To:     luto@...nel.org
Cc:     dave.hansen@...el.com, dave.hansen@...ux.intel.com,
        keescook@...omium.org, linux-kernel@...r.kernel.org,
        sroettger@...gle.com, x86@...nel.org
Subject: Re: PKU usage improvements for threads

> sys_sigaltstack() is already pretty much useless with SHSTK, and it’s kinda busted with AVX512. How about we just add a whole new non-kludgy API?

Hi, why is that useless? Signal is not going to change the SSP, all it needs to do is creating a token that can be restored by sigreturn in the future on the current shadow stack.
Can you provide some examples about that? Thank you.