[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1108097: marked as done (libffi: please build with static trampolines enabled)

Your message dated Tue, 09 Dec 2025 10:18:54 +0000
with message-id <E1vSuo2-0037bF-0k@fasolo.debian.org>
and subject line Bug#1108097: fixed in libffi 3.5.2-3
has caused the Debian Bug report #1108097,
regarding libffi: please build with static trampolines enabled
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1108097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108097
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libffi
Version: 3.4.8-2

Dear Maintainer(s),

Static trampolines support was disabled in 3.4.2-2 in d/rules via
--disable-exec-static-tramp. There was no bug mentioned, and the
package is not in git so no git commit either to explain the reason
for this.

This makes it impossible to use anything that relies on code integrity
(e.g.: IPE https://kernel.org/doc/html/latest/security/ipe.html ) and
disabling writable+executable memory like systemd's
MemoryDenyWriteExecute= sandboxing setting. Static trampolines were
added for the main architectures to support this use case. As far as I
can tell, on architectures where it's not supported the W+X
implementation will be used automatically as a fallback.

Please consider dropping --disable-exec-static-tramp from d/rules. Thanks.

--- End Message ---
--- Begin Message --- 
Source: libffi
Source-Version: 3.5.2-3
Done: Matthias Klose <doko@debian.org>

We believe that the bug you reported is fixed in the latest version of
libffi, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1108097@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose <doko@debian.org> (supplier of updated libffi package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 09 Dec 2025 10:57:00 +0100
Source: libffi
Architecture: source
Version: 3.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers <debian-gcc@lists.debian.org>
Changed-By: Matthias Klose <doko@debian.org>
Closes: 1108097
Changes:
 libffi (3.5.2-3) unstable; urgency=medium
 .
   * Stop building with --disable-exec-static-tramp. Closes: #1108097.
Checksums-Sha1:
 9be6395e7fc38d574dfe81d296aeef73ae313a9e 1954 libffi_3.5.2-3.dsc
 b8d7c59f7fdc59c9c2213438552f9ce5cfb310c4 10928 libffi_3.5.2-3.debian.tar.xz
 6797dee32cae7aa1a0c88fcc48b676cae5eca033 6591 libffi_3.5.2-3_source.buildinfo
Checksums-Sha256:
 ed67eb00402650aafdc76a7f491a64889fcf5b2da70c6bbb43ffab2e480cffc9 1954 libffi_3.5.2-3.dsc
 682fc1b23da5ece07584e30263c4dd178ebc819a8d8ec2ac5e5fd7c67c247d30 10928 libffi_3.5.2-3.debian.tar.xz
 88bec5d580f0bd0c62b395e205a182fb3da730a4d38be694ed1cdb9dce3c2925 6591 libffi_3.5.2-3_source.buildinfo
Files:
 37e0ae21b6a8d0501f5daeade2b9026a 1954 libs optional libffi_3.5.2-3.dsc
 99e4e7e872f4e2a9af7efed5287c115e 10928 libs optional libffi_3.5.2-3.debian.tar.xz
 187bdbcac3e2cc577df5dbc7290bffc3 6591 libs optional libffi_3.5.2-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmk38yMQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9fK7D/sHv87Xn2ZuNq9RyM+wXtIASW8EkIleUKZ2
aelbyKG0sh2sfzjFAmyqIHL0VP2WR+tA6tlc22lZ/4MrsvEvNtOlalSiBCieaXBD
qkH8vL2Xa7eUi830IACpZ7BirKOsMnjrlCbGdfLqkTXDiBhIzwNHotYwp5mmiKrM
7eGx7p4MKEWnwicAztKFR6eop2mok/66OVLGqHUjr+9wTWIk7BN6u/bm9MKRjef0
+OJBBPjZHSYvkqQ7gRyqYbfQ7Sq4RF/yYmqpcueLJDvUbcwav/XhVagQTfaaTrA0
oVNsKznY8oBw9FbRRcadBvRIXf7sQNTOHQGKUeEyUriG/oypWQ0utVTmi/eFZaE8
bx4x4Rk/tZ7l+ZUtPPan6awLP68/zcBiOTuu6EsTLmX2YRnrVq8aF9s29Z6bWAQ8
YPoxvHW50uPBAvmVmoRLJYcHqAIxjLfDDIPmHD3i7lBOwcAipVCytsXS6CpGSYcO
X8wyYvlDdWKX0aoYJBWtCOjKfcYoJjyPTU3I8RjLL1NrENzWkrKlYX0Urbi85ZLT
Y70KAHufoqKfd6H+h+FKpauY0JIYaJpWQzefj2S8WB/obP3lmTLmsFsPh8XFxSCT
isFzsLG3mtAXf/JH1YCVghMlUq1CabDx7nn9wJPlNk54FlnYjBJcV2JSLGC75qoX
7nkow3K7JQ==
=Lq0P
-----END PGP SIGNATURE-----

Attachment: pgp3_805HJRbv.pgp
Description: PGP signature


--- End Message ---
Reply to: