99fcd56135
The p11-kit remoting was initially introduced because softhsm was crashing during cleanup with OpenSSL 3.0. This was resolved since then and this code introduces a lot of complexity and possible bugs, such as when using the mechanisms from PKCS#11 3.0 that are unknown to the p11-kit remoting tool. It decides to remove them from the list as demonstrated here: https://github.com/p11-glue/p11-kit/issues/668 This resulted in pkcs11-provider not registering EDDSA siganture methods to the OpenSSL and failing when asked to provide a singature by the Ed25519 key from the PKCS#11 token. Signed-off-by: Jakub Jelen <jjelen@redhat.com> Reviewed-by: Sahana Prasad <sahana@redhat.com>
_ _ _ _
(_) (_) (_) (_)
(_) _ (_) _ _ _ _ _ (_) _
(_) (_) (_)(_) _ (_)(_) (_)(_) (_)(_) _
(_) (_) (_) (_) _ (_) _ (_) (_) (_)
(_) (_) (_)(_)(_) (_)(_) (_)(_) (_) (_).org
The SSH library
Why?
Why not ? :) I've began to work on my own implementation of the ssh protocol because i didn't like the currently public ones. Not any allowed you to import and use the functions as a powerful library, and so i worked on a library-based SSH implementation which was non-existing in the free and open source software world.
How/Who?
If you downloaded this file, you must know what it is : a library for accessing ssh client services through C libraries calls in a simple manner. Everybody can use this software under the terms of the LGPL - see the COPYING file
If you ask yourself how to compile libssh, please read INSTALL before anything.
Where ?
Contributing
Please read the file 'CONTRIBUTING.md' next to this README file. It explains our copyright policy and how you should send patches for upstream inclusion.
Have fun and happy libssh hacking!
The libssh Team