summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| | * | Merge branch '2.0' into 2.1Jeff Forcier2017-11-072-4/+7
| | |\ \ | | | |/
| | | * Changelog re #1108Jeff Forcier2017-11-071-0/+3
| | | | | | | | | | | | | | | | [ci skip]
| | | * Rename an internal-only 'async' method kwarg for Python 3.7 compatibility.Jeff Forcier2017-11-071-4/+4
| | | | | | | | | | | | | | | | Fixes #1108
| * | | Merge branch '2.1' into 2.2Jeff Forcier2017-10-182-0/+4
| |\ \ \ | | |/ /
| | * | Merge branch '2.0' into 2.1Jeff Forcier2017-10-182-0/+4
| | |\ \ | | | |/
| | | * Include LICENSE in wheelsJeff Forcier2017-10-182-0/+4
| | | |
| * | | Merge branch '2.1' into 2.2Jeff Forcier2017-10-101-1/+1
| |\ \ \ | | |/ /
| | * | Merge branch '2.0' into 2.1Jeff Forcier2017-10-101-1/+1
| | |\ \ | | | |/
| | | * TypofixJeff Forcier2017-10-101-1/+1
| | | |
| * | | Merge branch '2.1' into 2.2Jeff Forcier2017-09-262-3/+3
| |\ \ \ | | |/ /
| | * | Merge branch '2.0' into 2.1Jeff Forcier2017-09-262-3/+3
| | |\ \ | | | |/
| | | * sftp: fix BytesWarning: str() on a bytes instanceMichal Reznik2017-09-262-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | when running the code with python3 we get BytesWarning as what we receive from hexlify() function is bytes. Use u() from py3compat to overcome the issue. Fix: https://github.com/paramiko/paramiko/issues/1074
| * | | Merge branch '2.1' into 2.2Jeff Forcier2017-09-181-3/+9
| |\ \ \ | | |/ /
| | * | Merge branch '2.0' into 2.1Jeff Forcier2017-09-181-3/+9
| | |\ \ | | | |/
| | | * Note that #945 is 1.18+Jeff Forcier2017-09-181-0/+5
| | | | | | | | | | | | | | | | Also pulls in 1.17, 1.18 specific entries to the 2.x line. FML
| | | * Fix incorrect changelog branch stuff.Jeff Forcier2017-09-181-3/+4
| | | | | | | | | | | | | | | | Really starting to think we oughtta just move to one changelog file per major family :(
| * | | Cut 2.2.22.2.2Jeff Forcier2017-09-182-1/+2
| | | |
| * | | Merge branch '2.1' into 2.2Jeff Forcier2017-09-181-0/+1
| |\ \ \ | | |/ /
| | * | Cut 2.1.42.1.4Jeff Forcier2017-09-182-1/+2
| | | |
| * | | Merge branch '2.1' into 2.2Jeff Forcier2017-09-182-1/+2
| |\ \ \ | | |/ /
| | * | Merge branch '2.0' into 2.1Jeff Forcier2017-09-182-1/+2
| | |\ \ | | | |/
| | | * Need new twine for newer pypiJeff Forcier2017-09-181-1/+1
| | | |
| | | * Cut 2.0.72.0.7Jeff Forcier2017-09-182-1/+2
| | | |
| * | | Merge branch '2.1' into 2.2Jeff Forcier2017-09-181-0/+1
| |\ \ \ | | |/ /
| | * | Merge branch '2.0' into 2.1Jeff Forcier2017-09-181-0/+1
| | |\ \ | | | |/
| | | * Merge branch '2.0' of github.com:paramiko/paramiko into 2.0Jeff Forcier2017-09-1824-151/+513
| | | |\
| | | * | Migrate changelog release entry from 1.18Jeff Forcier2017-09-181-0/+1
| | | | |
| * | | | Changelog re #1065Jeff Forcier2017-09-181-0/+5
| | | | |
| * | | | Fix rekeying with GSS-API key exchangeSebastian Deiss2017-09-182-11/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When GSS-API key exchange is used a rekey caused a GSS-API MIC failure and closed the transport. This happened because the MIC of the transport session ID (H of the initial kex) was checked against the MIC of the new H created during rekey.
| * | | | Merge branch '2.1' into 2.2Jeff Forcier2017-09-127-90/+221
| |\ \ \ \ | | |/ / /
| | * | | Merge branch '2.0' into 2.1Jeff Forcier2017-09-127-90/+221
| | |\ \ \ | | | | |/ | | | |/|
| | | * | Changelog re #1061Jeff Forcier2017-09-121-0/+5
| | | | |
| | | * | Merge branch '2.0' into 1061-intJeff Forcier2017-09-125-11/+81
| | | |\ \
| | | | * | demo_simple: gss_auth and gss_kex are independent of each other.Anselm Kruis2017-09-121-4/+7
| | | | | |
| | | | * | Changelog re #1060Jeff Forcier2017-09-121-0/+3
| | | | | |
| | | | * | Merge branch '2.0' into 1060-intJeff Forcier2017-09-123-1/+65
| | | | |\ \
| | | | * | | Transport: fix the preferred KEX algorithms for gssapi-keyexAnselm Kruis2017-08-031-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add additional KEX algorithms for gssapi-keyex in front of the default preferred KEX algorithms, if gssapi-keyex is enabled. Before this change, Transport used a hard coded (and out-dated) list of algorithms, if gssapi-keyex was enabled.
| | | * | | | Pep8 and Sphinx fixes.Anselm Kruis2017-09-122-27/+29
| | | | | | |
| | | * | | | AuthHandler: handle local "gssapi-with-mic" errors in client modeAnselm Kruis2017-08-041-9/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Paramiko now tries other authentication methods, if "gssapi-with-mic" authentication may fails for a local reason (i.e. no kerberos ticket). Befor this change, any exception from the GSSAPI/SSPI caused the transport to be closed.
| | | * | | | AuthHandler: fix the server-mode "gssapi-with-mic" logicAnselm Kruis2017-08-043-53/+145
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A paramiko server is now able to handle a restart of the user authentication during the GSS-API token exchange. This may occur, if the client detects a local GSSAPI problem (e.g. a missing kerberos ticket) and continues with another authentication method. The added test case test_2_auth_trickledown still fails, because the paramiko client contains a bug too.
| | | * | | | Added paramiko.GSS_EXCEPTIONS: exception types used by GSSAPIAnselm Kruis2017-08-042-6/+17
| | | |/ / / | | | | | | | | | | | | | | | | | | | | | | | | This new constant is a tuple of the exception types used by the underlying GSSAPI/SSPI implementation.
| * | | | | Merge branch '2.1' into 2.2Jeff Forcier2017-09-120-0/+0
| |\ \ \ \ \ | | |/ / / /
| | * | | | Merge branch '2.0' into 2.1Jeff Forcier2017-09-121-0/+3
| | |\ \ \ \ | | | | |/ / | | | |/| |
| | | * | | Master changelog entry re: #1056 #1057 #1058 #1059Jeff Forcier2017-09-121-0/+3
| | | | | |
| * | | | | Master changelog entry re: #1056 #1057 #1058 #1059Jeff Forcier2017-09-121-0/+3
| | | | | |
| * | | | | Transport gssapi-keyex: set the gss_kex_used flag lateAnselm Kruis2017-08-042-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Set the flag gss_kex_used only after a gssapi-keyex has been successfully completed. This change prevents a wrong value in case of exceptions during the gssapi-keyex handshake.
| * | | | | Merge branch '2.1-gsskex-hostkeycheck-fix' into 2.2-gsskex-hostkeycheck-fixAnselm Kruis2017-08-042-13/+73
| |\ \ \ \ \ | | |/ / / /
| | * | | | Merge branch '2.0-gsskex-hostkeycheck-fix' into 2.1-gsskex-hostkeycheck-fixAnselm Kruis2017-08-042-13/+73
| | |\ \ \ \ | | | |/ / /
| | | * | | SSHClient: fix the host key testAnselm Kruis2017-08-042-1/+62
| | | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Skip the host key check only, if the transport actually used gssapi-keyex. Add tests for the missing-host-key RejectPolicy. Before this change, a man-in-the-middle attack on the paramiko ssh client with gss_kex=True was possible by having a server that does not support gssapi-keyex and gives any or no host key.
* | | | | changelog: update for #1039 / #1051Pierce Lopez2017-09-051-0/+3
| | | | |