Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

Rebuilt for Python 3.11

Update to 2.11.0
Align signature verification algorithm with OpenSSH re: zero-padding
implemented SSH servers handle
OpenSSH 7.7 and older has a bug preventing it from understanding how to
not keys), so when we added SHA2 support it broke all clients using
a version check is performed and the
Recent versions of Cryptography have deprecated Blowfish algorithm support;
Windows-native SSH agent support as merged in 2.10 could encounter
Add SSH config token expansion (eg '%h', '%p') when parsing 'ProxyJump'
Apply unittest 'skipIf' to tests currently using SHA1 in their critical

Update to 2.10.4
Update 'camelCase' method calls against the 'threading' module to be
'~paramiko.pkey.PKey' instances' '__eq__' did not have the usual safety
Servers offering certificate variants of hostkey algorithms (e.g.
rsa-cert-v01@openssh.com') could not have their host keys verified by
cert key types for that

Skip tests that would fail without SHA-1 signing support in backend, such as
9 (GH#2011)

Update to 2.10.3
Certificate-based pubkey auth was inadvertently broken when adding SHA2
Switch from module-global to thread-local storage when recording thread IDs
running processes (GH#2002, GH#2003)

Update to 2.10.2
Fix Python 2 compatibility breakage introduced in 2.10.1 (GH#2001)
Re-enable sftp tests, no longer failing under mock

Update to 2.10.1
CVE-2022-24302: Creation of new private key files using
using code would write out
incompatible
Add support for the '%C' token when parsing SSH config files (GH#1976)
Add support for OpenSSH's Windows agent as a fallback when Putty/WinPageant
Significantly speed up low-level read/write actions on
Add 'six' explicitly to install-requires; it snuck into active use at some
recently dropped it (GH#1985); this will be short-lived

Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild

Avoid use of deprecated python-mock by using unittest.mock instead

Update to 2.9.2
Connecting to servers that support 'server-sig-algs' but which have no
sha2-512' (since the use of
sig-algs' allows us to know what the server supports)
Enhanced log output when connecting to servers that do not support
sig-algs' extensions, making the new-as-of-2.9 defaulting to SHA2

Update to 2.9.1
Server-side support for 'rsa-sha2-256' and 'ssh-rsa' wasn't fully operable
sha2-512' instead) (GH#1935)

Update to 2.9.0
Add support for SHA-2 variants of RSA key verification algorithms (as
Client verification of server host key during key exchange will now prefer
sha2-512, rsa-sha2-256, and legacy ssh-rsa algorithms, in that order,
rsa
Note that the preference order of other algorithm families such as
Server mode will now offer all 3 RSA algorithms for host key verification
Client mode key exchange now sends the ext-info-c flag signaling support
sig-algs flag) has been added
Client mode, when performing public key authentication with an RSA key or
In all cases, the list of algorithms to consider is based on the new
512, SHA2-256 and SHA1, in that order
When the server does not send server-sig-algs, Paramiko will attempt
When the server does send server-sig-algs, the first algorithm
SSH agent support grew the ability to specify algorithm flags when
Server mode is now capable of pubkey auth involving SHA-2 signatures from
sig-algs only) to clients advertising ext-info-c in their key
'PKey.sign_ssh_data <paramiko.pkey.PKey>': Grew an extra, optional
rsa" for '~paramiko.rsakey.RSAKey')
A new '~paramiko.ssh_exception.SSHException' subclass was added,
'~paramiko.transport.Transport' grew a '_preferred_pubkeys' attribute and
focused,

Update to 2.8.1
Fix listdir failure when server uses a locale (GH#985, GH#992); now on
Deleting items from '~paramiko.hostkeys.HostKeys' would incorrectly raise
Update RSA and ECDSA key decoding subroutines to correctly catch exception
Update '~paramiko.pkey.PKey' and subclasses to compare ('__eq__') via
bit systems
bit Python 2, or a 32-bit Python 3 that is
Paramiko server processes would incorrectly authenticate the attacker
Paramiko client processes would incorrectly validate a connected server
in-the-middle attack. This impacts more users than the server-side

Update to 2.8.0
Administrivia overhaul, including but not limited to:
Migrate CI to CircleCI
Primary dev branch is now 'main' (renamed)
Many README edits for clarity, modernization etc.; including a bunch more
PyPI page much more fleshed out (long_description is now filled in with
flake8, pytest configs split out of setup.cfg into their own files
Invoke/invocations (used by maintainers/contributors) upgraded to modern
Newer server-side key exchange algorithms not intended to use SHA1
hellman-group14-sha256, diffie-hellman-group16-sha512) were
Add a 'prefetch' keyword argument to 'SFTPClient.get'/'SFTPClient.getfo' so

Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild