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]
Date:   Thu, 11 Apr 2019 14:24:10 +0200
From:   Florian Weimer <>
To:     Mathieu Desnoyers <>
Cc:     Will Deacon <>,
        libc-alpha <>,
        linux-kernel <>,
        Carlos O'Donell <>
Subject: Re: rseq/arm32: choosing rseq code signature

* Mathieu Desnoyers:

> /*
>  * TODO: document trap instruction objdump output on each sub-architecture
>  * instruction sets, as well as instruction set extensions.
>  */
> #define RSEQ_SIG 0x########

Will RSEQ_SIG actually be needed at run time outside the rseq
implementation library (whether it's glibc or something else)?

Actually rseq users will emit the signature directly into the text
section, right?  They never have to load it into a register, I assume.

My concern is that on some architectures, the very act of referencing
RSEQ_SIG will put it into the text section, as a non-instruction, which
is not what we want.


Powered by blists - more mailing lists