Index | Thread | Search

From:
"Theo de Raadt" <deraadt@openbsd.org>
Subject:
Re: devel/objfw: add BTCFI landing pads for amd64 and arm64
To:
Jonathan Schleifer <js@nil.im>
Cc:
Mark Kettenis <mark.kettenis@xs4all.nl>, tb@theobuehler.org, ports@openbsd.org, kettenis@openbsd.org
Date:
Sat, 24 Feb 2024 16:55:56 -0700

Download raw body.

Thread
  • Mark Kettenis:

    devel/objfw: add BTCFI landing pads for amd64 and arm64

  • Jonathan Schleifer <js@nil.im> wrote:
    
    > Fixed upstream:
    > https://objfw.nil.im/info/262baf76e7e66bc4
    > https://objfw.nil.im/info/d73a388ecaf73b2a
    > 
    > New release:
    > https://objfw.nil.im/downloads/objfw-1.0.10.tar.gz
    > https://objfw.nil.im/downloads/objfw-1.0.10.tar.gz.sig
    > 
    > Am 24.02.24 um 22:17 schrieb Mark Kettenis:
    > 
    > > Ah, right.  What happens in that case is that the branch will use
    > > register X16 or X17 and those are special in the sense that both "bti
    > > c" and "bti j" landing pads are ok.
    > 
    > Ah. Is that OpenBSD specific or on every OS? I used "bti jc" upstream
    > now to be on the safe side. I think security-wise it shouldn't make
    > much of a difference since it's still before the function prologue?
    
    Today: OpenBSD.
    
    In a few years, more and more software.
    
    In a decade, all operating systems.
    
    
    
  • Mark Kettenis:

    devel/objfw: add BTCFI landing pads for amd64 and arm64