29ad26db26
Use the new `-L` flag for the pkd tests so that they use a unique temporary directory for scratch space while running. Note the choice of `pkd_scratch_XXXXXX` in contrast to a path living under `/tmp`: by using a relative path, one can gather the full set of log artifacts from the GitLab CI jobs in the event that there is a test failure. The logs contain lots of information to help pinpoint what went wrong. Resolves https://gitlab.com/libssh/libssh-mirror/-/issues/143. Testing notes: - In the GitLab CI jobs I can see the flag being used, and can observe that I am able to gather the full set of detailed `pkd` logs in the event of a legitimate test failure. Signed-off-by: Jon Simons <jon@jonsimons.org> Reviewed-by: Jakub Jelen <jjelen@redhat.com> (cherry picked from commit 4f6aa53b16f9b5ad220006fc966e7829f360f97e)
_ _ _ _
(_) (_) (_) (_)
(_) _ (_) _ _ _ _ _ (_) _
(_) (_) (_)(_) _ (_)(_) (_)(_) (_)(_) _
(_) (_) (_) (_) _ (_) _ (_) (_) (_)
(_) (_) (_)(_)(_) (_)(_) (_)(_) (_) (_).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