public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
* [rpms/python-paramiko] f45: Update to 5.1.0 (rhbz#2554705)
@ 2026-10-18  9:28 Paul Howarth
  0 siblings, 0 replies; only message in thread
From: Paul Howarth @ 2026-10-18  9:28 UTC (permalink / raw)
  To: git-commits

            A new commit has been pushed.

            Repo   : rpms/python-paramiko
            Branch : f45
            Commit : fba1da590814be91d081aa102d6ec95977a66b01
            Author : Paul Howarth <paul@city-fan.org>
            Date   : 2026-10-18T10:16:20+01:00
            Stats  : +38/-7 in 4 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-paramiko/c/fba1da590814be91d081aa102d6ec95977a66b01?branch=f45

            Log:
            Update to 5.1.0 (rhbz#2554705)

- New upstream release 5.1.0
  - An API gap between '~paramiko.agent.AgentKey' and the other, 'concrete'
    '~paramiko.pkey.PKey' subclasses was triggering 'AttributeError' any time
    the agent-hosted key couldn't be loaded internally (an optional behavior
    that isn't, normally, required for successful auth) (GH#2462, GH#2465,
    GH#2475)
    - This could be due to new key types Paramiko doesn't yet support, or to
      bugs in loading types we do
    - The issue has been fixed by making sure '~paramiko.agent.AgentKey''s
      initialization behavior w.r.t. '.public_blob' matches those of its
      siblings; we've also made a related attribute access in
      '~paramiko.auth_handler.AuthHandler' more defensive, for good measure
  - The SHA2 transition left 'RSAKey.sign_ssh_data' incorrectly trying to look
    up its default signature algorithm via the key type's name string, which is
    still '"ssh-rsa"', and thus no longer a valid/implemented choice (which
    would be one of '"rsa-sha2-256[-cert...]"' or '"rsa-sha2-512[-cert...]"')
    (GH#2628)
    - This went unnoticed because most calls to this method have decided on an
      explicit signature algorithm during a protocol handshake and aren't
      relying on an implicit default; to restore that ability, this method now
      defaults to the strongest implemented algorithm, namely '"rsa-sha2-512"'
  - Added support for the 'mlkem768x25519-sha256' post-quantum hybrid key
    exchange method described in 'draft-ietf-sshm-mlkem-hybrid-kex'; it pairs
    ML-KEM-768 (FIPS 203) with X25519 and is interoperable with OpenSSH 10.0+;
    the new method is enabled automatically when the installed 'cryptography'
    library exposes ML-KEM (which requires OpenSSL 3.5+, AWS-LC, or BoringSSL);
    it is preferred over the existing classical methods when available
    - See 'paramiko.kex_mlkem.KexMLKEM768X25519'

---
diff --git a/.gitignore b/.gitignore
index 907f3a9..9c10363 100644
--- a/.gitignore
+++ b/.gitignore
@@ -56,3 +56,4 @@
 /paramiko-3.5.1.tar.gz
 /paramiko-4.0.0.tar.gz
 /paramiko-5.0.0.tar.gz
+/paramiko-5.1.0.tar.gz

diff --git a/0003-remove-pytest-relaxed-dep.patch b/0003-remove-pytest-relaxed-dep.patch
index 40952d9..b2d5bbe 100644
--- a/0003-remove-pytest-relaxed-dep.patch
+++ b/0003-remove-pytest-relaxed-dep.patch
@@ -1,14 +1,14 @@
 --- a/tests/test_client.py
 +++ b/tests/test_client.py
-@@ -33,7 +33,6 @@
- from unittest.mock import patch
+@@ -33,7 +33,6 @@ from tempfile import mkstemp
+ from unittest.mock import Mock, patch
  
  import pytest
 -from pytest_relaxed import raises
  
  import paramiko
  from paramiko import SSHClient
-@@ -710,10 +709,10 @@
+@@ -729,10 +728,10 @@ class PasswordPassphraseTests(ClientTest
  
      # TODO: more granular exception pending #387; should be signaling "no auth
      # methods available" because no key and no password
@@ -22,7 +22,7 @@
  
      def test_passphrase_kwarg_used_for_key_passphrase(self):
          # Straightforward again, with new passphrase kwarg.
-@@ -731,14 +730,14 @@
+@@ -750,14 +749,14 @@ class PasswordPassphraseTests(ClientTest
              password="television",
          )
  

diff --git a/python-paramiko.spec b/python-paramiko.spec
index 3d41619..ceea308 100644
--- a/python-paramiko.spec
+++ b/python-paramiko.spec
@@ -1,6 +1,6 @@
 Name:          python-paramiko
-Version:       5.0.0
-Release:       3%{?dist}
+Version:       5.1.0
+Release:       1%{?dist}
 Summary:       SSH2 protocol library for python
 
 # No version specified
@@ -86,6 +86,36 @@ PYTHONPATH=%{buildroot}%{python3_sitelib} pytest-%{python3_version}
 %doc html/
 
 %changelog
+* Sun Oct 18 2026 Paul Howarth <paul@city-fan.org> - 5.1.0-1
+- Update to 5.1.0 (rhbz#2554705)
+  - An API gap between '~paramiko.agent.AgentKey' and the other, 'concrete'
+    '~paramiko.pkey.PKey' subclasses was triggering 'AttributeError' any time
+    the agent-hosted key couldn't be loaded internally (an optional behavior
+    that isn't, normally, required for successful auth) (GH#2462, GH#2465,
+    GH#2475)
+    - This could be due to new key types Paramiko doesn't yet support, or to
+      bugs in loading types we do
+    - The issue has been fixed by making sure '~paramiko.agent.AgentKey''s
+      initialization behavior w.r.t. '.public_blob' matches those of its
+      siblings; we've also made a related attribute access in
+      '~paramiko.auth_handler.AuthHandler' more defensive, for good measure
+  - The SHA2 transition left 'RSAKey.sign_ssh_data' incorrectly trying to look
+    up its default signature algorithm via the key type's name string, which is
+    still '"ssh-rsa"', and thus no longer a valid/implemented choice (which
+    would be one of '"rsa-sha2-256[-cert...]"' or '"rsa-sha2-512[-cert...]"')
+    (GH#2628)
+    - This went unnoticed because most calls to this method have decided on an
+      explicit signature algorithm during a protocol handshake and aren't
+      relying on an implicit default; to restore that ability, this method now
+      defaults to the strongest implemented algorithm, namely '"rsa-sha2-512"'
+  - Added support for the 'mlkem768x25519-sha256' post-quantum hybrid key
+    exchange method described in 'draft-ietf-sshm-mlkem-hybrid-kex'; it pairs
+    ML-KEM-768 (FIPS 203) with X25519 and is interoperable with OpenSSH 10.0+;
+    the new method is enabled automatically when the installed 'cryptography'
+    library exposes ML-KEM (which requires OpenSSL 3.5+, AWS-LC, or BoringSSL);
+    it is preferred over the existing classical methods when available
+    - See 'paramiko.kex_mlkem.KexMLKEM768X25519'
+
 * Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 5.0.0-3
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
 

diff --git a/sources b/sources
index 2a1f63c..fffd912 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (paramiko-5.0.0.tar.gz) = 8130c0341e6ab39e8eb0f5ad187ecda2fb14db44995ccffbc3db0bb3cd568daca750224c3cbf4724b7ac503624b2fa72e78ad57e2218e69d471a43cfa8b4e63e
+SHA512 (paramiko-5.1.0.tar.gz) = 1bce7825c55de6b485242003b6264fbb5133128b0041c0a93bcd7847bccc58b45bffc35815aad8dd44f6285ba939e1a81a460a21845b77af8ceef8029c16ec82

^ permalink raw reply related	[flat|nested] only message in thread

only message in thread, other threads:[~2026-10-18  9:28 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-10-18  9:28 [rpms/python-paramiko] f45: Update to 5.1.0 (rhbz#2554705) Paul Howarth

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox