Displaying 4 results from an estimated 4 matches for "ssh2_msg_local_min".
2023 Apr 09
2
"Bad packet length 1231976033"
...start with this which are sent with error() or fatal() 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"
...() or fatal() 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.
>
2008 Feb 09
1
Problems connecting with SSH2
Hello,
I've been using OpenSSH 3.6.1p2 for quite some time at work. We have a
firewall, and I had no problems connecting to external machines.
Today my machine was updated to version 4.1p1 and it has a problem.
When I try to make an SSH2 connection to an external machine,
everything seems to work right up to the very end:
debug1: Authentication succeeded (publickey)
debug1: channel