public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Daniel Mellado <dmellado@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/bpfman] rawhide: Bump vendored openssl to 0.10.78 / openssl-sys to 0.9.117 for OpenSSL 4.0 support
Date: Wed, 22 Jul 2026 13:35:41 GMT [thread overview]
Message-ID: <178472734107.1.1808887000775680179.rpms-bpfman-1b0636d0d126@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/bpfman
Branch : rawhide
Commit : 1b0636d0d126f33c0bffa02dcaebc0468cb985df
Author : Daniel Mellado <dmellado@fedoraproject.org>
Date : 2026-07-22T12:21:38+02:00
Stats : +31/-6 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/bpfman/c/1b0636d0d126f33c0bffa02dcaebc0468cb985df?branch=rawhide
Log:
Bump vendored openssl to 0.10.78 / openssl-sys to 0.9.117 for OpenSSL 4.0 support
Re-vendor dependencies with openssl crate versions that support OpenSSL 4.x,
fixing the FTBFS caused by the f45 mass rebuild against openssl-devel 4.0.1.
Resolves: rhbz#2503790
Signed-off-by: Daniel Mellado <dmellado@fedoraproject.org>
---
diff --git a/0006-bump-openssl-to-0.10.78-openssl4-support.patch b/0006-bump-openssl-to-0.10.78-openssl4-support.patch
new file mode 100644
index 0000000..f23c02b
--- /dev/null
+++ b/0006-bump-openssl-to-0.10.78-openssl4-support.patch
@@ -0,0 +1,26 @@
+--- c/Cargo.lock 2026-07-22 10:32:21.908588477 +0200
++++ w/Cargo.lock 2026-07-22 10:32:51.061123715 +0200
+@@ -2705,9 +2705,9 @@
+
+ [[package]]
+ name = "openssl"
+-version = "0.10.70"
++version = "0.10.78"
+ source = "registry+https://github.com/rust-lang/crates.io-index"
+-checksum = "61cfb4e166a8bb8c9b55c500bc2308550148ece889be90f609377e58140f42c6"
++checksum = "f38c4372413cdaaf3cc79dd92d29d7d9f5ab09b51b10dded508fb90bb70b9222"
+ dependencies = [
+ "bitflags 2.6.0",
+ "cfg-if",
+@@ -2737,9 +2737,9 @@
+
+ [[package]]
+ name = "openssl-sys"
+-version = "0.9.105"
++version = "0.9.117"
+ source = "registry+https://github.com/rust-lang/crates.io-index"
+-checksum = "8b22d5b84be05a8d6947c7cb71f7c849aa0f112acd4bf51c2a7c1c988ac0a9dc"
++checksum = "b47e7e6bb2c38cd930d25a23b40fa52e068c10e85f3e03a7f5ba5aaca5713695"
+ dependencies = [
+ "cc",
+ "libc",
diff --git a/bpfman.spec b/bpfman.spec
index b25d2e3..1bdeb1a 100644
--- a/bpfman.spec
+++ b/bpfman.spec
@@ -45,11 +45,9 @@ License: %{shrink:
URL: https://bpfman.io
Source0: https://github.com/bpfman/bpfman/archive/refs/tags/v%{version}.tar.gz
-# References to code related to the p434 curve have been removed from the vendored sources in Source1
-# In order to generate the vendored file run "cargo vendor --versioned dirs"
-# remove "fiat-crypto-0.2.9/src/p434.rs" and references to it
-# removed forbidden Unicode code points (RTLO 0x202E) from idna-0.5.0 IdnaTestV2.txt
-# compress with "tar -Jcvf"
+# In order to generate the vendored file run "cargo vendor --versioned-dirs"
+# remove "fiat-crypto-0.2.9/src/p434_64.rs" and its reference in lib.rs
+# then compress with "tar -Jcf bpfman-<version>-vendor.tar.xz vendor/"
# Source1: https://github.com/marioferh/ebpf_sources/raw/refs/heads/bpfman-0.5.4/bpfman-0.5.4-vendor.tar.xz
Source1: bpfman-%{version}-vendor.tar.xz
Patch0: 0001-bump-cargo-lock-for-idna-1-0-3.diff
@@ -57,6 +55,7 @@ Patch1: 0002-bump-openssl-to-0.10.70-CVE-2025-0977.patch
Patch2: 0003-bump-quinn-proto-to-0.11.14-CVE-2026-31812.patch
Patch3: 0004-bump-tar-to-0.4.45-CVE-2026-33056.patch
Patch4: 0005-bump-time-to-0.3.47-CVE-2026-25727.patch
+Patch5: 0006-bump-openssl-to-0.10.78-openssl4-support.patch
# aya-obj doesn't compile in x86
ExcludeArch: %{ix86}
diff --git a/sources b/sources
index 037c26d..a63eb51 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (bpfman-0.5.4-vendor.tar.xz) = 798c953bb44e0681a56c1d2d549216494ad58aa0e25bd89bd400a80446915c787c6c887ca6cd71d22d2645629952bd8e618c6f60bd5b06e5d769ec69f1f412d4
+SHA512 (bpfman-0.5.4-vendor.tar.xz) = de7bcafe593a7d1ef0c9feb741e69db58dc114f53174ca352cbde1d3fbcd97444d0a8fd245b281e1802d1c593a96bed97070e6c11cbf89b9179d094cf98ab538
SHA512 (v0.5.4.tar.gz) = 5b9df9b1f9b8924a7bb80d51c2d4cfa01d6b4a739d74f989b05e22b6dd93dace80f1d97434cda410395bd1f39bc22c12f134f45a31c209e1322fd6a3571028dd
reply other threads:[~2026-07-22 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178472734107.1.1808887000775680179.rpms-bpfman-1b0636d0d126@fedoraproject.org \
--to=dmellado@fedoraproject.org \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox