AsyncSSH 2.4.0 released!

4 views
Skip to first unread message

Ron Frederick

unread,
Aug 29, 2020, 6:51:01 PM8/29/20
to asyncssh...@googlegroups.com, asyncssh-users
AsyncSSH version 2.4.0 is now available on Github and PyPI, with bug fixes and enhancements. Here’s a list of changes since 2.3.0:

* Added support for accessing keys through a PKCS#11 provider, allowing
keys on PIV security tokens to be used directly by AsyncSSH without
the need to run an SSH agent. X.509 certificates can also be retrieved
from the security token and used with SSH servers which support that.

* Added support for using Ed25519 and Ed448 keys in X.509 certificates,
and the corresponding SSH certificate and signature algorithms.
Certificates can use these keys as either subject keys or signing keys,
and certificates can be generated by either AsyncSSH or by OpenSSL
version 1.1.1 or later.

* Added support for feed_data() and feed_eof() methods in SSHReader,
mirroring methods of the same name in asyncio's StreamReader to
improve interoperability between the two APIs. Thanks go to Mikhail
Terekhov for suggesting this and providing an example implementation.

* Updated unit tests to test interoperability with OpenSSL 1.1.1 when
reading and writing Ed25519 and Ed448 public and private key files.
Previously, due to lack of support in OpenSSL, AsyncSSH could only
test against OpenSSH, and only in OpenSSH key formats. With OpenSSL
1.1.1, testing is now also done using PKCS#8 format.

* Fixed config file parser to properly ignore all comment lines, even
if the lines contain unbalanced quotes.

* Removed a note about the lack of a timeout parameter in the AsyncSSH
connect() method, now that it supports a login_timeout argument.
Thanks go to Tomasz Drożdż for catching this.

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