On Tue, 11 Jan 2022 at 17:06, zadig wrote:
>
> > Because qemu-user is specifically emulating a Linux kernel.
> > We don't want to provide a million tweakable command line options,
> > it gets unmaintainable very quickly. We just want to provide the
> > process with the environment that the Linux k
Because qemu-user is specifically emulating a Linux kernel.
We don't want to provide a million tweakable command line options,
it gets unmaintainable very quickly. We just want to provide the
process with the environment that the Linux kernel gives it.
Yes, I agree.
That's system emulation, whi
On Tue, 11 Jan 2022 at 16:33, zadig wrote:
>
> Thanks for your celerity.
>
> > The architecture specifies that the number of bits used for the
> > signature depends on various properties of the CPU and of
> > the configuration that the host OS has put it into.
> Yes, this is why I checked for the
Thanks for your celerity.
The architecture specifies that the number of bits used for the
signature depends on various properties of the CPU and of
the configuration that the host OS has put it into.
Yes, this is why I checked for the TCR value, because basically it only
depends on its value an
On Tue, 11 Jan 2022 at 15:28, zadig wrote:
>
> Hello,
>
> I am running some dummy aarch64 ELF I have built using clang with
> -mbranch-protection=pac-ret+leaf+b-key.
>
> qemu successfully emulates the code, however the pointer authentication
> signature seems weird to me: only one byte is used for
Hello,
I am running some dummy aarch64 ELF I have built using clang with
-mbranch-protection=pac-ret+leaf+b-key.
qemu successfully emulates the code, however the pointer authentication
signature seems weird to me: only one byte is used for the signature.
Here is an example:
FE 07 C1 DA PAC
