summaryrefslogtreecommitdiffhomepage
path: root/sites/docs
diff options
context:
space:
mode:
authorJeff Forcier <jeff@bitprophet.org>2014-02-21 14:31:08 -0800
committerJeff Forcier <jeff@bitprophet.org>2014-02-21 14:31:08 -0800
commit0e9a5a4b463fbbc8518e4679850207e31fbd8a0f (patch)
treeb35c2eeaba1b82747b7db931f53c060a464baf64 /sites/docs
parentf836c98e5c5c859cb9d0189aed51dd5a884ee072 (diff)
Move module level docstring into Sphinx docs
Diffstat (limited to 'sites/docs')
-rw-r--r--sites/docs/index.rst22
1 files changed, 22 insertions, 0 deletions
diff --git a/sites/docs/index.rst b/sites/docs/index.rst
index 98f4069a..87a0f994 100644
--- a/sites/docs/index.rst
+++ b/sites/docs/index.rst
@@ -10,6 +10,28 @@ please see `the main website <http://paramiko.org>`_.
API documentation
=================
+The high-level client API starts with creation of an `.SSHClient` object. For
+more direct control, pass a socket (or socket-like object) to a `.Transport`,
+and use `start_server <.Transport.start_server>` or `start_client
+<.Transport.start_client>` to negotiate with the remote host as either a server
+or client.
+
+As a client, you are responsible for authenticating using a password or private
+key, and checking the server's host key. (Key signature and verification is
+done by paramiko, but you will need to provide private keys and check that the
+content of a public key matches what you expected to see.)
+
+As a server, you are responsible for deciding which users, passwords, and keys
+to allow, and what kind of channels to allow.
+
+Once you have finished, either side may request flow-controlled `channels
+<.Channel>` to the other side, which are Python objects that act like sockets,
+but send and receive data over the encrypted session.
+
+For details, please see the following tables of contents (which are organized
+by area of interest.)
+
+
Core SSH protocol classes
-------------------------