Fork of paramiko for Python 3 migration.
Go to file
Scott Maxwell 2d738fa08b Fix winapi 2013-10-30 17:09:50 -07:00
demos Fix imports 2013-10-30 16:19:30 -07:00
images [project @ Arch-1:robey@lag.net--2005-master-shake%paramiko--dev--1--patch-1] 2005-04-18 01:59:15 +00:00
paramiko Fix winapi 2013-10-30 17:09:50 -07:00
tests Fix message sending 2013-10-30 17:09:34 -07:00
.bzrignore [project @ robey@lag.net-20080706223938-fn82xx2k0zvklazm] 2008-07-06 15:39:38 -07:00
.gitignore Merge pull request #105 from clarete/master 2013-02-03 11:22:25 -08:00
.travis.yml Add Py3.2 and Py3.3 to travis 2013-10-30 16:02:01 -07:00
ChangeLog.0 [project @ Arch-1:robey@lag.net--2005-master-shake%paramiko--dev--1--patch-11] 2005-05-21 20:42:29 +00:00
ChangeLog.1 [project @ Arch-1:robey@lag.net--2005-master-shake%paramiko--dev--1--patch-11] 2005-05-21 20:42:29 +00:00
LICENSE Fix FSF address 2012-09-23 16:16:57 -07:00
MANIFEST.in [project @ robey@lag.net-20061031185035-b57ad8184c39063a] 2006-10-31 10:50:35 -08:00
Makefile Make docs target build whenever Paramiko files change 2012-11-28 22:18:31 -08:00
NEWS Merge branch '1.11' 2013-09-27 21:57:42 -07:00
NOTES [project @ Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-33] 2004-03-09 01:09:17 +00:00
README Add explicit link to updated API docs. Fixes #160 2013-04-28 18:41:10 -07:00
TODO Take ownership of TODO file 2012-09-23 14:34:40 -07:00
dev-requirements.txt Uncap the requirements 2013-10-30 16:07:30 -07:00
fabfile.py Tag nag 2013-08-01 11:50:46 -07:00
setup.py Merge branch '1.11' 2013-09-27 21:29:59 -07:00
setup_helper.py Fixed a typo in the license header of most files 2013-09-27 21:29:18 -07:00
test.py Fix imports 2013-10-30 16:19:30 -07:00
tox.ini Add Py3.2 and Py3.3 to tox 2013-10-30 16:06:09 -07:00

README

========
paramiko
========

:Paramiko: Python SSH module
:Copyright: Copyright (c) 2003-2009  Robey Pointer <robeypointer@gmail.com>
:Copyright: Copyright (c) 2013  Jeff Forcier <jeff@bitprophet.org>
:License: LGPL
:Homepage: https://github.com/paramiko/paramiko/
:API docs: http://docs.paramiko.org


What
----

"paramiko" is a combination of the esperanto words for "paranoid" and
"friend".  it's a module for python 2.5+ that implements the SSH2 protocol
for secure (encrypted and authenticated) connections to remote machines.
unlike SSL (aka TLS), SSH2 protocol does not require hierarchical
certificates signed by a powerful central authority. you may know SSH2 as
the protocol that replaced telnet and rsh for secure access to remote
shells, but the protocol also includes the ability to open arbitrary
channels to remote services across the encrypted tunnel (this is how sftp
works, for example).

it is written entirely in python (no C or platform-dependent code) and is
released under the GNU LGPL (lesser GPL). 

the package and its API is fairly well documented in the "doc/" folder
that should have come with this archive.


Requirements
------------

  - python 2.5 or better <http://www.python.org/>
  - pycrypto 2.1 or better <https://www.dlitz.net/software/pycrypto/>

If you have setuptools, you can build and install paramiko and all its
dependencies with this command (as root)::

    easy_install ./


Portability
-----------

i code and test this library on Linux and MacOS X. for that reason, i'm
pretty sure that it works for all posix platforms, including MacOS. it
should also work on Windows, though i don't test it as frequently there.
if you run into Windows problems, send me a patch: portability is important
to me.

some python distributions don't include the utf-8 string encodings, for
reasons of space (misdirected as that is). if your distribution is
missing encodings, you'll see an error like this::

    LookupError: no codec search functions registered: can't find encoding

this means you need to copy string encodings over from a working system.
(it probably only happens on embedded systems, not normal python
installs.) Valeriy Pogrebitskiy says the best place to look is
``.../lib/python*/encodings/__init__.py``.


Bugs & Support
--------------

Please file bug reports at https://github.com/paramiko/paramiko/. There is currently no mailing list but we plan to create a new one ASAP.


Demo
----

several demo scripts come with paramiko to demonstrate how to use it.
probably the simplest demo of all is this::

    import paramiko, base64
    key = paramiko.RSAKey(data=base64.decodestring('AAA...'))
    client = paramiko.SSHClient()
    client.get_host_keys().add('ssh.example.com', 'ssh-rsa', key)
    client.connect('ssh.example.com', username='strongbad', password='thecheat')
    stdin, stdout, stderr = client.exec_command('ls')
    for line in stdout:
        print '... ' + line.strip('\n')
    client.close()

...which prints out the results of executing ``ls`` on a remote server.
(the host key 'AAA...' should of course be replaced by the actual base64
encoding of the host key.  if you skip host key verification, the
connection is not secure!)

the following example scripts (in demos/) get progressively more detailed:

:demo_simple.py:
    calls invoke_shell() and emulates a terminal/tty through which you can
    execute commands interactively on a remote server.  think of it as a
    poor man's ssh command-line client.

:demo.py:
    same as demo_simple.py, but allows you to authenticiate using a
    private key, attempts to use an SSH-agent if present, and uses the long
    form of some of the API calls.

:forward.py:
    command-line script to set up port-forwarding across an ssh transport.
    (requires python 2.3.)

:demo_sftp.py:
    opens an sftp session and does a few simple file operations.

:demo_server.py:
    an ssh server that listens on port 2200 and accepts a login for
    'robey' (password 'foo'), and pretends to be a BBS.  meant to be a
    very simple demo of writing an ssh server.

:demo_keygen.py:
    an key generator similar to openssh ssh-keygen(1) program with
    paramiko keys generation and progress functions.

Use
---

the demo scripts are probably the best example of how to use this package.
there is also a lot of documentation, generated with epydoc, in the doc/
folder.  point your browser there.  seriously, do it.  mad props to
epydoc, which actually motivated me to write more documentation than i
ever would have before.

there are also unit tests here::

    $ python ./test.py

which will verify that most of the core components are working correctly.