2011-03-24 14:38:50 +03:00
|
|
|
|
_ _ _ _
|
|
|
|
|
(_) (_) (_) (_)
|
|
|
|
|
(_) _ (_) _ _ _ _ _ (_) _
|
|
|
|
|
(_) (_) (_)(_) _ (_)(_) (_)(_) (_)(_) _
|
|
|
|
|
(_) (_) (_) (_) _ (_) _ (_) (_) (_)
|
|
|
|
|
(_) (_) (_)(_)(_) (_)(_) (_)(_) (_) (_).org
|
|
|
|
|
|
|
|
|
|
The SSH library
|
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
2009-09-22 18:51:28 +04:00
|
|
|
|
|
2005-07-05 05:21:44 +04:00
|
|
|
|
1* 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.
|
2009-09-22 18:51:28 +04:00
|
|
|
|
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.
|
2005-07-05 05:21:44 +04:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2* 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
|
|
|
|
|
|
2009-09-22 18:51:28 +04:00
|
|
|
|
If you ask yourself how to compile libssh, please read INSTALL before anything.
|
2005-07-05 05:21:44 +04:00
|
|
|
|
|
2009-09-22 18:51:28 +04:00
|
|
|
|
3* Where ?
|
2005-07-05 05:21:44 +04:00
|
|
|
|
-_-_-_-_-_-_
|
|
|
|
|
|
2009-06-16 18:45:39 +04:00
|
|
|
|
http://www.libssh.org
|
2009-10-14 00:23:06 +04:00
|
|
|
|
|
|
|
|
|
4* API Changes !
|
|
|
|
|
-_-_-_-_-_-_-_-_-_
|
|
|
|
|
|
2010-12-21 17:24:38 +03:00
|
|
|
|
Changes between 0.4 and 0.5
|
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
We use the ssh_ prefix as namespace for every function now. There is a legacy.h
|
|
|
|
|
which could be used to get the old function names.
|
|
|
|
|
|
2009-10-14 00:23:06 +04:00
|
|
|
|
Changes between 0.3 and 0.4
|
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
|
|
We changed libssh to be typesafe now:
|
|
|
|
|
|
|
|
|
|
SSH_SESSION *session -> ssh_session session
|
|
|
|
|
SFTP_SESSION *sftp -> sftp_session sftp
|
|
|
|
|
CHANNEL *channel -> ssh_channel channel
|
|
|
|
|
STRING *string -> ssh_string string
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
The options structure has been removed and there is a new function. This
|
|
|
|
|
function can set all available options now. You can find the enum in the
|
|
|
|
|
header file and it is documented. Example:
|
|
|
|
|
|
|
|
|
|
ssh_options_set(session, SSH_OPTIONS_HOST, "localhost");
|
|
|
|
|
|
2010-04-06 23:14:52 +04:00
|
|
|
|
5* Copyright policy
|
|
|
|
|
-_-_-_-_-_-_-_-_-_-_
|
|
|
|
|
|
|
|
|
|
The developers of libssh have a policy of asking for contributions to be made
|
|
|
|
|
under the personal copyright of the contributor, instead of a corporate
|
|
|
|
|
copyright.
|
|
|
|
|
|
|
|
|
|
There are some reasons for the establishment of this policy:
|
|
|
|
|
|
|
|
|
|
* Individual copyrights make copyright registration in the US a simpler
|
|
|
|
|
process.
|
|
|
|
|
* If libssh is copyrighted by individuals rather than corporations,
|
|
|
|
|
decisions regarding enforcement and protection of copyright will, more
|
|
|
|
|
likely, be made in the interests of the project, and not in the interests
|
|
|
|
|
of any corporation’s shareholders.
|
|
|
|
|
* If we ever need to relicense a portion of the code contacting individuals
|
|
|
|
|
for permission to do so is much easier than contacting a company.
|