1
0
Fork
You've already forked libssh
0
No description
  • C 93.7%
  • CMake 4.2%
  • C++ 1.5%
  • Shell 0.4%
  • Makefile 0.2%
Find a file
2012年11月27日 19:58:54 +01:00
build build: Added a --clang option. 2011年02月07日 13:34:37 +01:00
cmake/Modules cmake: Make CHECK_C_COMPILER_FLAG_SSP a function. 2011年07月29日 11:37:52 +02:00
contrib compile fpic stuff as .lo 2011年12月31日 01:51:40 +01:00
doc doc: Add OpenSSH pub certkey auth. 2011年07月19日 12:20:36 +02:00
examples examples: Fix permissions of the file we copy. 2011年08月03日 22:21:43 +02:00
include add ssh_buffer_get_size and ssh_buffer_get_data 2012年01月07日 00:20:46 +01:00
src CVE-2012-4562 2012年11月27日 19:58:54 +01:00
tests pki: Improve ssh_pki_import_privkey_base64(). 2011年08月08日 15:28:31 +02:00
.clang_complete vim: Added .clang_complete file. 2011年02月07日 17:39:06 +01:00
.gitignore updated .gitignore 2011年12月31日 13:19:23 +01: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 build: Update ChangeLog. 2011年06月01日 17:55:26 +02:00
CMakeLists.txt cmake: Added pkg-config support for libssh_treads. 2011年06月14日 13:47:04 +02:00
config.h.cmake [crypto] initial support for ecdh-sha2-nistp256 2011年06月13日 13:46:34 +02:00
ConfigureChecks.cmake Check for ecdsa with openssl, added log_warning 2011年06月12日 19:38:42 +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: Increased version numbers. 2011年02月10日 12:54:33 +01:00
CTestConfig.cmake ctest: Set the memcheck suppression file correctly. 2010年12月19日 16:30:23 +01:00
DefineOptions.cmake Set variables in the good order 2010年12月28日 13:50:34 +01:00
INSTALL doc: Added samplessh hint to INSTALL. 2010年12月21日 16:21:02 +01:00
libssh.pc.cmake Add pkg-config file libssh.pc 2009年12月30日 19:05:48 +01:00
libssh_threads.pc.cmake build: Fix libssh_threads pkg-config. 2011年06月15日 18:26:51 +02:00
README doc: Extremly important README update! 2011年03月25日 19:24:42 +01:00

 _ _ _ _
 (_) (_) (_) (_)
 (_) _ (_) _ _ _ _ _ (_) _
 (_) (_) (_)(_) _ (_)(_) (_)(_) (_)(_) _
 (_) (_) (_) (_) _ (_) _ (_) (_) (_)
 (_) (_) (_)(_)(_) (_)(_) (_)(_) (_) (_).org
 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.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.
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 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.