Displaying 5 results from an estimated 5 matches for "sshpkt_disconnect".
2023 Apr 09
2
"Bad packet length 1231976033"
...atal() or
fprint(stderr, ...), but two which stand out as being a bit different:
# kex.c
?invalid:
??????????????? send_error(ssh, "Invalid SSH identification string.");
# packet.c
??????? if (*typep < SSH2_MSG_MIN || *typep >= SSH2_MSG_LOCAL_MIN) {
??????????????? if ((r = sshpkt_disconnect(ssh,
??????????????????? "Invalid ssh2 packet type: %d", *typep)) != 0 ||
If it happens to be either of these, then the tcpdump showing the
exchange prior to this point would be enlightening.
2023 Apr 09
1
"Bad packet length 1231976033"
I have a cron script that polls various machines for their configs and archives any changes.
When it connects to an OpenWrt router running "OpenSSH_9.1p1, OpenSSL 1.1.1s 1 Nov 2022", it sometimes gets this error:
Bad packet length 1231976033.
ssh_dispatch_run_fatal: Connection to 192.168.8.1 port 22: message authentication code incorrect
What's odd is that the length is *always*
2023 Apr 23
1
"Bad packet length 1231976033"
...stand out as being a bit different:
>
> # kex.c
>
> invalid:
> send_error(ssh, "Invalid SSH identification string.");
>
> # packet.c
>
> if (*typep < SSH2_MSG_MIN || *typep >= SSH2_MSG_LOCAL_MIN) {
> if ((r = sshpkt_disconnect(ssh,
> "Invalid ssh2 packet type: %d", *typep)) != 0 ||
>
> If it happens to be either of these, then the tcpdump showing the exchange prior to this point would be enlightening.
>
2020 Mar 24
4
ZSTD compression support for OpenSSH
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
2020 Sep 05
8
[PATCH 0/5] ZSTD compression support for OpenSSH
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