search for: ssh_msg_userauth_success

...MSG_USERAUTH_REQUEST Method name: publickey Boolean: TRUE SSH_MSG_USERAUTH_FAILURE Supported auth. methods: password, publickey Partial success Boolean: TRUE SSH_MSG_USERAUTH_REQUEST Method name: password Boolean: FALSE SSH_MSG_USERAUTH_SUCCESS After this the client opens a channel and the interactive session gets established. OpenSSH client 6.4p1 Embedded SSH server SSH_MSG_USERAUTH_REQUEST Method name: none SSH_MSG_USERAUTH_FAILURE Supported auth. methods: password, publickey...

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> The "zstd at breakpoint.cc" compression algorithm enables ZSTD based compression as defined in RFC8478. The compression is delayed until the server sends the SSH_MSG_USERAUTH_SUCCESS which is the same time as with the "zlib at openssh.com" method. Signed-off-by: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> --- cipher.c | 30 +++++- configure.ac | 8 ++ kex.c | 5 + kex.h | 3 + myproposal.h | 2 +- packet.c | 272 ++++++...

I added ZSTD support to OpenSSH roughly three years ago and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

I hacked zstd support into OpenSSH a while ago and just started to clean it up in the recent days. The cleanup includes configuration support among other things that I did not have. During testing I noticed the following differences compared to zlib: - highly interactive shell output (as in refreshed at a _very_ high rate) may result in higher bandwidth compared to zlib. Since zstd is quicker

I added ZSTD support to OpenSSH roughly over a year and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

Dear all, For my thesis, I've been working on automatic inference of state machines for SSH servers. I ran into a couple of particularities regarding OpenSSH's inferred state machine, and was hoping some of you might be interested. Maybe you can even shed some light on it. Setup: I'm using LearnLib's (Java) version of the L* learning algorithm [1] to come up with sequences of