I checked the upstream changes between 2.8.1 (jammy version) and 2.9.3: https://github.com/paramiko/paramiko/compare/2.8.1...2.9.3
There are only a few commits: * Weird typos introduced 2 years ago, bah (only change to test cases) * Longterm TODOs (adds only comments) * Enhance kex DEBUG logging to be more readable * Add support for RSA SHA2 host and public keys (we want this one) * Add agent RSA-SHA2 support, also tweak changelog w/ more tickets (we want this one too) * Changelog format tweak (only doc update) * Cut 2.9.0 * Changelog and test re #1955 (we want this one) * Fix #1955 (we want this one) * Cut 2.9.1 * Add more visible backwards compat warning re 2.9 RSA2 changes (only doc update) * Fix up logging and exception handling re: pubkey auth and presence/lack of server-sig-algs (we want this one) * Cut 2.9.2 * Clarify disabled algorithms keys vs pubkeys in changelog (only doc update) * Fix publickey authentication with signed RSA key (we want this one) * Changelog closes #1963, closes #1977 (only doc update) * util: store thread assigned id in thread-local storage, fixes #2002 (we want this one) * Changelog re #2002, re #2003, closes #2002 (only doc update) * Cut 2.9.3 Result: The difference between 2.8 and 2.9 is basically the RSA2 support that we want/need. Only the commit "Enhance kex DEBUG logging to be more readable" is not needed. So I say let's update the paramiko package to 2.9.3 instead of "backporting" the change. For the SRUs we might only backport the client side support which is a smaller patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961979 Title: Can't connect to Jammy hosts (openssh >= 8.8p1-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/1961979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
