1
1
The SSH library (LGPL license) https://www.libssh.org
Перейти к файлу
2010-12-20 15:45:49 +01:00
benchmarks New benchmarks directory 2010-12-19 18:56:16 +01:00
build build: Fixed options parsing. 2010-09-08 16:29:50 +02:00
cmake/Modules build: Added -pedantic-errors. 2010-09-10 21:46:36 +02:00
doc doc: Started to write a linking howto. 2010-12-10 20:17:57 +01:00
examples example: Fixed gcc warning. 2010-12-18 14:05:06 +01:00
include include: Only require LIBSSH_STATIC on Windows. 2010-12-10 20:02:15 +01:00
src build: Fixed some build warnings on FreeBSD. 2010-12-20 15:45:49 +01:00
tests New benchmarks directory 2010-12-19 18:56:16 +01:00
.gitignore Add a git ignore file. 2009-06-19 10:25:51 +02:00
AUTHORS updated changelog + authors 2009-05-18 18:39:26 +00:00
BSD added a file from openssh needed for known host parsing 2008-11-02 23:46:55 +00:00
ChangeLog Added changelog entries for 0.4 rc2. 2009-11-20 16:11:17 +01:00
CMakeLists.txt New benchmarks directory 2010-12-19 18:56:16 +01:00
config.h.cmake build: Fixed checking for printf function on Windows. 2010-09-02 11:50:21 +02:00
ConfigureChecks.cmake cmake: Fixed a problem with ccache. 2010-10-19 11:50:29 +02:00
COPYING legal paperwork to be 100% respectful of LGPL, about openssl's 2008-06-16 13:58:56 +00:00
CPackConfig.cmake build: Added a check for NSIS. 2010-08-03 18:13:59 +02:00
CTestConfig.cmake ctest: Set the memcheck suppression file correctly. 2010-12-19 16:30:23 +01:00
DefineOptions.cmake New benchmarks directory 2010-12-19 18:56:16 +01:00
INSTALL Improve the INSTALL file. 2009-05-07 08:32:50 +00:00
libssh.pc.cmake Add pkg-config file libssh.pc 2009-12-30 19:05:48 +01:00
README Added the copyright policy to the README. 2010-04-07 11:29:47 +02:00

Этот файл содержит неоднозначные символы Юникода

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

libssh: the SSH library
~~~~~~~~~~~~~~~~~~~~~~~

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.
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.


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

If you ask yourself how to compile libssh, please read INSTALL before anything.

3* Where ?
-_-_-_-_-_-_

http://www.libssh.org

4* API Changes !
-_-_-_-_-_-_-_-_-_

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");

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 corporations 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.