AsyncSSH 2.2.0 released!

3 views
Skip to first unread message

Ron Frederick

unread,
Feb 29, 2020, 7:08:08 PM2/29/20
to asyncssh...@googlegroups.com, asyncssh-users
AsyncSSH version 2.2.0 is now available on Github and PyPI, with with bug fixes and enhancements. Here’s a list of changes since 2.1.0:

* Added support for U2F/FIDO2 security keys, with the following capabilities:

* ECDSA (NISTP256) and Ed25519 key algorithms
* Key generation, including control over the application and user the
key is associated with and whether touch is required when using the key
* Certificate generation, both as a key being signed and a CA key
* Resident keys, allowing security keys to be used on multiple machines
without any information being stored outside of the key
* Access to and management of keys loaded in an OpenSSH ssh-agent
* Support for both user and host keys and certificates
* Support for "no-touch-required" option in authorized_keys files
* Support for "no-touch-required" option in OpenSSH certificates
* Compatibility with security key support added in OpenSSH version 8.2

* Added login timeout client option and limits on the length and number
of banner lines AsyncSSH will accept prior to the SSH version header.

* Improved load_keypairs() to read public key files, confirming that they
are consistent with their associated private key when they are present.

* Fixed issues in the SCP server related to handling filenames with spaces.

* Fixed an issue with resuming reading after readuntil() returns an
incomplete read.

* Fixed a potential issue related to asyncio not reporting sockname/peername
when a connection is closed immediately after it is opened.

* Made SSHConnection a subclass of asyncio.Protocol to please type checkers.

Downloads can be found in the usual place:

Home page: http://asyncssh.readthedocs.io
PyPI: https://pypi.python.org/pypi/asyncssh
GitHub: https://github.com/ronf/asyncssh

Please let me know if you have any questions or problems with this new release.
--
Ron Frederick
ro...@timeheart.net



Reply all
Reply to author
Forward
0 new messages