public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Alexander Sosedkin <asosedkin@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/crypto-policies] rawhide: Update from upstream (ML-KEM SSH, ...)
Date: Mon, 08 Jun 2026 11:06:27 GMT	[thread overview]
Message-ID: <178091678734.1.10932774656089411122.rpms-crypto-policies-f59e390b8cd0@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/crypto-policies
            Branch : rawhide
            Commit : f59e390b8cd07f123b24e63ee2ebe872bfa3cf5d
            Author : Alexander Sosedkin <asosedkin@redhat.com>
            Date   : 2026-03-31T20:35:25+02:00
            Stats  : +12/-5 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/crypto-policies/c/f59e390b8cd07f123b24e63ee2ebe872bfa3cf5d?branch=rawhide

            Log:
            Update from upstream (ML-KEM SSH, ...)

- FIPS: allow NIST hybrid kexes for openssh
- libssh: enable NIST ML-KEM hybrids
- libssh: add sntrup761x25519-sha512/mlkem768x25519-sha256
- openssl: prefix every group and sigalg with a ?

---
diff --git a/crypto-policies.spec b/crypto-policies.spec
index b230ea3..193aa3f 100644
--- a/crypto-policies.spec
+++ b/crypto-policies.spec
@@ -1,5 +1,5 @@
-%global git_date 20251128
-%global git_commit 19878fea4c5f62208655e32269842bce55c819b2
+%global git_date 20260331
+%global git_commit 4c567b2a200f1c23076c4c09bf7a5d380ed36ae6
 %{?git_commit:%global git_commit_hash %(c=%{git_commit}; echo ${c:0:7})}
 
 %global _python_bytecompile_extra 0
@@ -11,7 +11,7 @@
 
 Name:           crypto-policies
 Version:        %{git_date}
-Release:        3.git%{git_commit_hash}%{?dist}
+Release:        1.git%{git_commit_hash}%{?dist}
 Summary:        System-wide crypto policies
 
 License:        LGPL-2.1-or-later
@@ -37,8 +37,9 @@ BuildRequires: systemd-rpm-macros
 Conflicts: openssl-libs < 1:3.5.0-1
 Conflicts: nss < 3.105
 Conflicts: libreswan < 3.28
-Conflicts: openssh < 9.9
+Conflicts: openssh < 10.0
 Conflicts: gnutls < 3.8.10
+Conflicts: libssh < 0.12
 
 # Most users want this, the split is mostly for Fedora CoreOS
 Recommends: crypto-policies-scripts
@@ -289,6 +290,12 @@ exit 0
 %{_datarootdir}/crypto-policies/python
 
 %changelog
+* Tue Mar 31 2026 Alexander Sosedkin <asosedkin@redhat.com> - 20260331-1.git4c567b2
+- FIPS: allow NIST hybrid kexes for openssh
+- libssh: enable NIST ML-KEM hybrids
+- libssh: add sntrup761x25519-sha512/mlkem768x25519-sha256
+- openssl: prefix every group and sigalg with a ?
+
 * Fri Jan 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 20251128-3.git19878fe
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
 

diff --git a/sources b/sources
index efdfdf3..beaf6ec 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (crypto-policies-git19878fe.tar.gz) = a9e99938c7c647b1625e302c189af5ef3fde3fc2182a9ccfb275636712b10dd85ce91f2f3b36b0a63fef23b3d0065a409e3cc71f3ee4fbe2688b19bd34b80ec7
+SHA512 (crypto-policies-git4c567b2.tar.gz) = 2b6252fca3b31dcd2ee93876797add7a59ea02a1e0485c823e7745a2e4c736ae26f520fb89bbe5253d0f701e9dfe356c9c5b73fa81ce5ce8c9e26cef1b22557c

                 reply	other threads:[~2026-06-08 11:06 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=178091678734.1.10932774656089411122.rpms-crypto-policies-f59e390b8cd0@fedoraproject.org \
    --to=asosedkin@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