[root@gnu-tgl-1 hjl]# rpm -qf /lib64/libgcrypt.so.20 libgcrypt-1.9.2-2.fc34.x86_64 [root@gnu-tgl-1 hjl]# readelf -n /lib64/libgcrypt.so.20 | grep feature [root@gnu-tgl-1 hjl]# [hjl@gnu-efi-2 ~]$ rpm -qf /lib64/libgcrypt.so.20 libgcrypt-1.8.7-1.fc33.x86_64 [hjl@gnu-efi-2 ~]$ readelf -n /lib64/libgcrypt.so.20 | grep feature x86 feature: IBT, SHSTK [hjl@gnu-efi-2 ~]$
Hi, do you have some hints where do these come from (compiler flags, configuration?)? Does it work with new 1.9.3 version? https://bodhi.fedoraproject.org/updates/FEDORA-2021-54a91de592
ok, the version 1.9.3 is not any better: [root@fedora34 ~]# readelf -n /lib64/libgcrypt.so.20 | grep feature Probably this? https://src.fedoraproject.org/rpms/libgcrypt/c/8c18517a2519c8acbf705612db701c063990ff59 I read it as it is available in master already. Unfortunately, there is no better reference. Let me check.
Let me take a look to fix it.
This patch: https://gitlab.com/cet-software/libgcrypt/-/commit/b04c0a86b19856071c29d2a6285f3240c606ee7a should work.
Thank you. I verified that the local build has the expected flags. Did you submit the patch upstream already or should I do that?
(In reply to Jakub Jelen from comment #5) > Thank you. I verified that the local build has the expected flags. > > Did you submit the patch upstream already or should I do that? https://lists.gnupg.org/pipermail/gcrypt-devel/2021-April/005147.html
FEDORA-2021-46873b3b46 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-46873b3b46
FEDORA-2021-46873b3b46 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-46873b3b46` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-46873b3b46 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-46873b3b46 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.