similar to: Bad packet length rarely but still too often

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*

Hi, I'm trying to get OpenSSH to work on Solaris 10 wich Sun C 5.8 compiler (SUNWspro 11). I've compiled OpenSSL 0.9.8a without problem and OpenSSH 4.3p2 as well. [user at compilationserver ~/openssh-4.3p2] ./ssh -V OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005 My problem is that I cannot connect to anything. When I try I always get an error [user at compilationserver ~/openssh-4.3p2]

Hi, I've just upgraded to openssh-4.7p1 on my gentoo box, and I've noticed a incompatibility with openssh-3.6.1p2 running on a redhat AS3 server. If I ssh from my openssh-4.7_p1 client to the openssh-3.6.1p2 server, and RemoteForward a port, the ssh connection closes if I try to send more than roughly 300K through the tunneled port. The problem isn't present when I use openssh-4.6p1

Hi, I've just upgraded to openssh-4.7p1 on my gentoo box, and I've noticed a incompatibility with openssh-3.6.1p2 running on a redhat AS3 server. If I ssh from my openssh-4.7_p1 client to the openssh-3.6.1p2 server, and RemoteForward a port, the ssh connection closes if I try to send more than roughly 300K through the tunneled port. The problem isn't present when I use openssh-4.6p1

After upgrading my client with 2.4p1, I started getting the folowing errors when using slogin to login to a server: 2f 75 73 72 2f 6c 6f 63 Disconnecting: Bad packet length 796226418. Thinking it was the 2.4 upgrade, I uninstalled 2.4 and reinstalled 2.3 client. Problem still exists. I have OpenSSH 2.3 installed as the server. I even deleted the key entry on the client side by editing the

Hi I'm having huge problems with OpenSSH 3.0.1p1, compiled with OpenSSL 0.9.6b 9 Jul 2001 and running with prngd_0.9.23, it disconnects unexpectedly during client session due to bad packet length and corrupted MAC on input, according to debug anyway. What can cause this kinds of errors? I've verified that both se9104/server and switch runs in 100 Mbit full duplex and switch statstictics

Hello, I am porting the Openssh3.4 code to a proprietary operating system. I am running into the issue of ssh client disconnecting with a message - Disconnecting: Bad packet length 2782384553. This happens only when there is a large (~100k) output of some command executed on the remote system. If the output is not large then it doesn't happen. I tried with different encryption algorithm

Hello, I have the following problem with ssh on Solaris 10, 64bitx86 systems: bash-3.00# ssh -v admin at 172.20.11.244 OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to 172.20.11.244 [172.20.11.244] port 22. debug1: Connection established. debug1: identity

On 09/04/2023 02:20, Philip Prindeville wrote: > What's odd is that the length is*always* 1231976033 (which is 0x496E7661 or "Inva" in ASCII). Could you get a tcpdump when this happens? Then maybe more of the error can be captured. I grepped for Inva in the source code. There are lots of error messages which start with this which are sent with error() or fatal() or

Brian Candler wrote: > > What's odd is that the length is *always* 1231976033 (which is > > 0x496E7661 or "Inva" in ASCII). > > Could you get a tcpdump when this happens? Or debug output from at least the client (run ssh with -vvv) or preferably the server (run sshd with -ddd). //Peter

Sorry about taking so long to get back to you. The problem is sporadic and I've had other fires to put out first... Here's a PCAP of authentication failures: https://www.redfish-solutions.com/misc/kvm1.pcap > On Apr 9, 2023, at 1:21 AM, Brian Candler <b.candler at pobox.com> wrote: > > On 09/04/2023 02:20, Philip Prindeville wrote: >> What's odd is that the

> On Apr 10, 2023, at 7:24 AM, Darren Tucker <dtucker at dtucker.net> wrote: > > On Mon, 10 Apr 2023 at 07:07, Peter Stuge <peter at stuge.se> wrote: >> >> Brian Candler wrote: >>>> What's odd is that the length is *always* 1231976033 (which is >>>> 0x496E7661 or "Inva" in ASCII). > > One thing that can cause this is

> On Apr 10, 2023, at 7:24 AM, Darren Tucker <dtucker at dtucker.net> wrote: > > On Mon, 10 Apr 2023 at 07:07, Peter Stuge <peter at stuge.se> wrote: >> >> Brian Candler wrote: >>>> What's odd is that the length is *always* 1231976033 (which is >>>> 0x496E7661 or "Inva" in ASCII). > > One thing that can cause this is

On Tue, 25 Apr 2023 at 03:36, Philip Prindeville <philipp_subx at redfish-solutions.com> wrote: > > On Apr 10, 2023, at 7:24 AM, Darren Tucker <dtucker at dtucker.net> wrote: [...] > > Since you're using 9.1, the message could be an "Invalid free", since > > there was a double-free bug in that release :-( > > Forgot to ask: does this bug manifest

Hi, OpenSSH coredump was seen on our customer's side causing ssh login slow and manual command not workable. We need help to identify the root cause. Thanks!! >> Background: 1) server info: # uname -a SunOS owtnmncccm0cnmo 5.10 Generic_125100-10 sun4v sparc SUNW,Netra-CP3060 bash-3.00# /usr/local/bin/ssh -v OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007 bash-3.00# cat

NEW message w/ URL to zip archive containing debug output. Hi I'm having huge problems with OpenSSH 3.0.1p1, compiled with OpenSSL 0.9.6b 9 Jul 2001 and running with prngd_0.9.23, it disconnects unexpectedly during client session due to bad packet length and corruped MAC on input, according to debug anyway. What can cause this kinds of errors? I've verified that both se9104/server and

I haven't been able to get scp to work with RedHat 6.2 (select: Bad file descriptor), so... I tried upgrading with openssh-2.3.0p1-1.src.rpm and openssl-0.9.5a-3.src.rpm No joy. When running just ssh, I get "Disconnecting: Bad packet length 795178083." This seems to be a problem with sshd, since the 2.3 ssh client will work fine with a 2.1 server (but not scp, which still gives

On Mon, 10 Apr 2023 at 07:07, Peter Stuge <peter at stuge.se> wrote: > > Brian Candler wrote: > > > What's odd is that the length is *always* 1231976033 (which is > > > 0x496E7661 or "Inva" in ASCII). One thing that can cause this is if the libc writes to stderr (ie fd 2) on some classes of error. This is something libc should probably not do, since

Hello, I just built openssh-2.5.2p2 on an HP running HP-UX 11.00. Seems now when I try and connect to other HP's running ssh with version openssh-2.3.0p1 (using protocol version 2), I'm getting disconnected because of a "Bad packet length" error: ssh -v isd1 ... debug1: ssh_dss_verify: signature correct debug1: Wait SSH2_MSG_NEWKEYS. debug1: GOT SSH2_MSG_NEWKEYS. debug1: send

it seems that this check does not work on solaris #if BYTE_ORDER != LITTLE_ENDIAN #define BYTE_SWAP #endif could you please check that BYTE_SWAP is defined in rijndael.c -m