public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Frantisek Krenzelok <fkrenzel@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/nss] f43: Update NSS to 3.126.0
Date: Fri, 31 Jul 2026 09:59:10 GMT [thread overview]
Message-ID: <178549195064.1.3380623922984807263.rpms-nss-9eac0ccdf8e3@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/nss
Branch : f43
Commit : 9eac0ccdf8e341d226c3707861309db2262822fa
Author : Frantisek Krenzelok <fkrenzel@redhat.com>
Date : 2026-07-30T15:51:50+02:00
Stats : +7/-4 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/nss/c/9eac0ccdf8e341d226c3707861309db2262822fa?branch=f43
Log:
Update NSS to 3.126.0
---
diff --git a/nss.spec b/nss.spec
index 7901005..f89ae63 100644
--- a/nss.spec
+++ b/nss.spec
@@ -1,13 +1,13 @@
%global nspr_version 4.39.0
-%global nss_version 3.125.0
+%global nss_version 3.126.0
# NOTE: To avoid NVR clashes of nspr* packages:
# - reset %%{nspr_release} to 1, when updating %%{nspr_version}
# - increment %%{nspr_version}, when updating the NSS part only
-%global baserelease 2
+%global baserelease 1
%global nss_release %baserelease
# use "%%global nspr_release %%[%%baserelease+n]" to handle offsets when
# release number between nss and nspr are different.
-%global nspr_release %[%baserelease+1]
+%global nspr_release %[%baserelease+2]
# only need to update this as we added new
# algorithms under nss policy control
%global crypto_policies_version 20240521
@@ -1097,6 +1097,9 @@ fi
%changelog
+* Thu Jul 30 2026 Frantisek Krenzelok <fkrenzel@redhat.com> - 3.126.0-1
+- Update NSS to 3.126.0
+
* Sat Jul 25 2026 Rostislav Krasny <rostiprodev@gmail.com> - 3.125.0-2
- Reseed the freebl DRBG after fork() so forked children do not replay the
parent's random stream (Firefox fork server duplicate UUIDs / crypto output)
diff --git a/sources b/sources
index 4ecf218..3c9b9c6 100644
--- a/sources
+++ b/sources
@@ -1,4 +1,4 @@
SHA512 (blank-cert9.db) = 2f8eab4c0612210ee47db8a3a80c1b58a0b43849551af78c7da403fda3e3d4e7757838061ae56ccf5aac335cb54f254f0a9e6e9c0dd5920b4155a39264525b06
SHA512 (blank-key4.db) = 8fedae93af7163da23fe9492ea8e785a44c291604fa98e58438448efb69c85d3253fc22b926d5c3209c62e58a86038fd4d78a1c4c068bc00600a7f3e5382ebe7
SHA512 (nss-3.118-ml-dsa-test-for-sign-verify-pkcs12_files.tar.xz) = c6440f332703ca9a3351be5a35eac42f24b9c114f54137b95691aa353cc329f0fb7016b689b2f976bc6cff66aa62760067f3226efad665a5252f37294a3d12a6
-SHA512 (nss-3.125-with-nspr-4.39.tar.gz) = 383929a735dc49f7a75547f83f6cfd8047ed5f20e78b936bc2f34d7c2fc6a036b1c37a9c2c335a49809d702c0fcd8e2b07f5e224dee82b7b152ce53ab9c3f705
+SHA512 (nss-3.126-with-nspr-4.39.tar.gz) = 521f5dd5e09d66f0bd946e0ea90502d7bf4de4f26d67f993c0dc82c881b3f5758a218bd58941d2423a729342bc8d73d404c8fb92f0d0bb7d136095954641a860
reply other threads:[~2026-07-31 9:59 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=178549195064.1.3380623922984807263.rpms-nss-9eac0ccdf8e3@fedoraproject.org \
--to=fkrenzel@redhat.com \
--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