Age | Commit message (Collapse) | Author |
|
|
|
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.
|
|
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.
|
|
|
|
Fixes #967 #968
Rollup of earlier branches proposed as #969 and #970 with
additional fix inside sftp_client.
Includes new tests for SFTPFile usage.
Change against the 1.17 branch.
|
|
Fixes #968
Changes the behaviour of the underlying asbytes helper to
pass along unknown types. Most callers already handle this
by passing the bytes along to a file or socket-like object
which will raise TypeError anyway.
Adds test coverage through the Transport implementation.
Change against the 1.17 branch.
|
|
|
|
Fixes #967
Also adds test coverage for writing various types to
BufferedFile which required some small changes to the test
LoopbackFile subclass.
Change against the 1.17 branch.
|
|
|
|
|
|
|
|
ensures all defaults key/cipher/digest etc types are supported
|
|
|
|
|
|
Honestly not sure WTF
|
|
|
|
continuations
|
|
|
|
|
|
is not defined
This changes define the proper Timer expired error message instead of raising
AttributeError when errno.ETIME is not available on the platform. fixes #862
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Every other merge screws them up anyway.
|
|
|
|
The SSH protocol allows the client to transmit environment variables to
the server. This is particularly useful if the user wants to modify the
environment of an executed command without having to reexecute the
actual command from a shell.
This patch extends the Client and Channel interface to allow
the transmission of environment variables to the server side.
In order to use this feature the SSH server must accept environment
variables from the client (e.g. the AcceptEnv configuration directive of
OpenSSH).
FROM BITPROPHET: backport cherry-pick to 1.x line
|
|
|
|
|
|
Re #520
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Previously only 256-bit was handled and in certain cases (private key
reading) 384- and 521-bit keys were treated as 256-bit keys causing
silent errors.
Tests have been added to specifically test the 384 and 521 keysizes. As
RFC 5656 defines 256, 384, and 521 as the required keysizes this seems a
good set to test. Also, this will cover the branches at ecdsakey.py:55.
Test keys were renamed and test_client.py was modified as a result.
This also fixes two bugs in ecdsakey.py. First, when calculating bytes
needed to store a key, the assumption was made that the key size (in
bits) was divisible by 8 (see line 137). This has been fixed by rounding
up (wasn't an issue as only 256-bit keys were used before). Another bug
was that the key padding in asbytes was being done backwards (was
padding on current_length - needed_length bytes).
|
|
|
|
|
|
|
|
Because "Unable to connect to port 22 on or X.X.X.X" looks seriously
_weird_ with the blank space between "on" and "or".
|
|
Fixes #617.
|