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:   Sun, 24 May 2020 16:44:40 -0700
To:     Sasha Levin <>
CC:     Thomas Gleixner <>,
        Don Porter <>,
        Jarkko Sakkinen <>,
        Andi Kleen <>,,,,,,,
Subject: Re: Re: [PATCH v12 00/18] Enable FSGSBASE instructions

On May 24, 2020 2:19:45 PM PDT, Sasha Levin <> wrote:
>On Sun, May 24, 2020 at 12:45:18PM -0700, wrote:
>>There are legitimate reasons to write a root-hole module, the main one
>being able to test security features like SMAP. I have requested before
>a TAINT flag specifically for this purpose, because TAINT_CRAP is
>nowhere near explicit enough, and is also used for staging drivers.
>Call it TAINT_TOXIC or TAINT_ROOTHOLE; it should always be accompanied
>with a CRIT level alert.
>What I don't like about our current system of TAINT_* flags is that
>while we can improve it as much as we want, no one outside of the
>tree seems to be using it. While Thomas may have been commenting on
>Graphene's behaviour, look at any other code that did the same thing:
>- Graphene:
>- Occlum:
>None of which set even the CRAP flag.

That's a separate problem, but I would personally want to have it for my own test modules in case one ever escapes.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Powered by blists - more mailing lists