Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On 2023-12-14 14:04:08 -0500, Greg Wooledge wrote: > On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > > I have the latest version!!! I recall that this is a Debian/unstable > > machine, which I upgrade regularly. So, everytime I get such an error, > > I have the latest client. >

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On Thu, Dec 14, 2023 at 05:14:28PM +0100, Vincent Lefevre wrote: > I have the latest version!!! I recall that this is a Debian/unstable > machine, which I upgrade regularly. So, everytime I get such an error, > I have the latest client. Just for the record, saying you have the "latest" version of

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Vincent Lefevre wrote: > I have the latest version!!! I recall that this is a Debian/unstable > machine, which I upgrade regularly. So, everytime I get such an error, > I have the latest client. > > Note also that this is an error that occurs randomly. Then I'm sorry, that I can't help you more o

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

On 2023-12-14 17:03:10 +0100, Klaus Singvogel wrote: > Vincent Lefevre wrote: > > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent > > errors like > > > > kex_exchange_identification: read: Connection reset by peer > > Connection reset by x.x.x.x port 22 > > This sounds most like

Re: openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Vincent Lefevre wrote: > Since 2 years (from early 2022 to 2023-11-26), I've got recurrent > errors like > > kex_exchange_identification: read: Connection reset by peer > Connection reset by x.x.x.x port 22 This sounds most likely that your SSH client (program at your local machine) has an outda

openssh: missing kex_exchange_identification ssh error messages with 1:9.5p1-2?

Since 2 years (from early 2022 to 2023-11-26), I've got recurrent errors like kex_exchange_identification: read: Connection reset by peer Connection reset by x.x.x.x port 22 or kex_exchange_identification: Connection closed by remote host Connection closed by x.x.x.x port 22 But yesterday, the

Re: [Bulk] Re: ssh error - Write failed: Broken pipe

On 24/05/12 04:24 AM, elbbit wrote: On 23/05/12 22:45, Gary Dale wrote: On 23/05/12 04:53 PM, elbbit wrote: On your server put this line in your sshd_config after "Port 22": Port 443 Do a "service ssh restart" or "/etc/init.d/ssh restart". Connect using: ssh -p 443 user@host That has the

Re: ssh error - Write failed: Broken pipe

Karl E. Jorgensen wrote: > I've seen that before and it took us ages to narrow down - in our case > (admittedly your case may be different), it was the combination of > network interface MTU and packet fragmentation. I was just going to suggest exactly the same thing. And it took us ages to track

Re: ssh error - Write failed: Broken pipe

On Wed, May 23, 2012 at 08:25:20PM +0100, Gary Dale wrote: > On 23/05/12 03:07 PM, elbbit wrote: > > On 23/05/12 19:46, Gary Dale wrote: > >> This is repeatable 100% of the time. > > I get this error on my ISP. I have found they are inspecting the > > internet packets and terminating if there is t

Re: ssh error - Write failed: Broken pipe

Hi - entering this thread late... On Wed, May 23, 2012 at 07:46:29PM +0100, Gary Dale wrote: > I'm connecting at various times to different Debian/Squeeze servers from > my Debian/Wheezy workstation using ssh. No matter which server I connect > to, I find that if I move a lot of data on the remo

Re: [Bulk] Re: ssh error - Write failed: Broken pipe

On 23/05/12 22:45, Gary Dale wrote: > On 23/05/12 04:53 PM, elbbit wrote: >> On your server put this line in your sshd_config after "Port 22": >> >> Port 443 >> >> Do a "service ssh restart" or "/etc/init.d/ssh restart". Connect using: >> >> ssh -p 443 user@host >> > That has the same issue as the

Re: ssh error - Write failed: Broken pipe

On 23/05/12 03:25 PM, Gary Dale wrote: On 23/05/12 03:07 PM, elbbit wrote: On 23/05/12 19:46, Gary Dale wrote: This is repeatable 100% of the time. I get this error on my ISP. I have found they are inspecting the internet packets and terminating if there is too little back-and-forth traffic.

Re: [Bulk] Re: ssh error - Write failed: Broken pipe

On 23/05/12 04:53 PM, elbbit wrote: On 23/05/12 20:25, Gary Dale wrote: On 23/05/12 03:07 PM, elbbit wrote: On 23/05/12 19:46, Gary Dale wrote: This is repeatable 100% of the time. I get this error on my ISP. I have found they are inspecting the internet packets and terminating if there is t

Re: ssh error - Write failed: Broken pipe

On 23/05/12 20:25, Gary Dale wrote: > On 23/05/12 03:07 PM, elbbit wrote: >> On 23/05/12 19:46, Gary Dale wrote: >>> This is repeatable 100% of the time. >> I get this error on my ISP. I have found they are inspecting the >> internet packets and terminating if there is too little back-and-forth >>

Re: ssh error - Write failed: Broken pipe

On 23/05/12 03:07 PM, elbbit wrote: On 23/05/12 19:46, Gary Dale wrote: This is repeatable 100% of the time. I get this error on my ISP. I have found they are inspecting the internet packets and terminating if there is too little back-and-forth traffic. My ISP is a mobile phone network over 3

Re: ssh error - Write failed: Broken pipe

On 23/05/12 19:46, Gary Dale wrote: > This is repeatable 100% of the time. I get this error on my ISP. I have found they are inspecting the internet packets and terminating if there is too little back-and-forth traffic. My ISP is a mobile phone network over 3G so they are probably trying to keep

ssh error - Write failed: Broken pipe

I'm connecting at various times to different Debian/Squeeze servers from my Debian/Wheezy workstation using ssh. No matter which server I connect to, I find that if I move a lot of data on the remote server, I get kicked out of my ssh session with a "Write failed: Broken pipe" error. This does

Re: ssh error

On Mon, Aug 23, 2010 at 05:09:01PM +0700, Vit wrote: > I've fount the core problem. > Software modifies LD_LIBRARY_PATH, and there is another libkrb5support.so.0 > in it, which doesn't contain needed paths. > How to solve this problem without modifyind the proprietary software? > With best regards

Re: ssh error

I've fount the core problem. Software modifies LD_LIBRARY_PATH, and there is another libkrb5support.so.0 in it, which doesn't contain needed paths.How to solve this problem without modifyind the proprietary software?With best regards,Koroteev Victor.-- 

Re: ssh error

On Mon, 23 Aug 2010 14:30:00 +0700, Boyd Stephen Smith Jr. wrote: On Monday 23 August 2010 01:34:13 Vit wrote: /usr/bin/ssh: relocation error: /usr/lib/libkrb5.so.3: symbol krb5int_utf8_lentab, version krb5support_0_MIT not defined in file libkrb5support.so.0 with link time reference Seems

Re: ssh error

On Monday 23 August 2010 01:34:13 Vit wrote: > /usr/bin/ssh: relocation error: /usr/lib/libkrb5.so.3: symbol > krb5int_utf8_lentab, version krb5support_0_MIT not defined in file > libkrb5support.so.0 with link time reference Seems to be in the library here. $ objdump -tT /usr/lib/libkrb5support.s

Re: ssh error

Vit writes: > krb5int_utf8_lentab, version krb5support_0_MIT not defined in file Google search for this finds http://ibot.rikers.org/%23debian/20091126.html.gz where the issue was solved by reinstalling a few libraries. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a

ssh error

Dear debian-users!We have 4 squeeze servers in cluster and with some non-free software installed. Hostbased ssh authorization is used and working on manual connections. But if the software tries to connect to another computer (through perl script) there is an error:/usr/bin/ssh: relocation error

kerberos & ssh error message

Hello folks, system: etch64 ssh -vvv -o PreferredAuthentications=gssapi-with-mic [EMAIL PROTECTED] debug3: preferred gssapi-with-mic debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: debug2: Unrecognized authentication method name: gssapi-with-mic debug1: No more authentica

Re: ssh error "Disconnecting: Bad packet length 3265385124."

On 2004-03-28 04:16:03 +0200, Vincent Lefevre wrote: > On 2004-03-27 16:21:08 +, Colin Watson wrote: > > Details? (ssh client/server version, ssh -vvv output) > > Client: OpenSSH_3.8p1 Debian 1:3.8p1-2, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar > 2004 [...] Hmm... looking at the date, mor

Re: ssh error "Disconnecting: Bad packet length 3265385124."

On 2004-03-27 16:21:08 +, Colin Watson wrote: > Details? (ssh client/server version, ssh -vvv output) Client: OpenSSH_3.8p1 Debian 1:3.8p1-2, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004 Server: sshd version OpenSSH_3.4p1 Debian 1:3.4p1-1.woody.3 This problem is not reproducible. As I

Re: ssh error "Disconnecting: Bad packet length 3265385124."

On 2004-03-27 13:48:49 +0100, Klaus Thielking-Riechert wrote: > Maybe your ssh server only supports ssh version 1 and your client > wants to use version 2. No, both use version 2. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: - 100% validated (X)HTML - Acorn Risc PC, Yel

Re: ssh error "Disconnecting: Bad packet length 3265385124."

On Sat, Mar 27, 2004 at 12:09:52PM +0100, Vincent Lefevre wrote: } A ssh connection was closed due to the following error: } } Disconnecting: Bad packet length 3265385124. } } Where does this come from? Is it a bug? I have experienced this same problem. I have two machines behind a NAT/firewal

Re: ssh error "Disconnecting: Bad packet length 3265385124."

On Sat, Mar 27, 2004 at 12:09:52PM +0100, Vincent Lefevre wrote: > A ssh connection was closed due to the following error: > > Disconnecting: Bad packet length 3265385124. > > Where does this come from? Is it a bug? Details? (ssh client/server version, ssh -vvv output) -- Colin Watson

Re: ssh error "Disconnecting: Bad packet length 3265385124."

On Saturday 27 March 2004 12:09, Vincent Lefevre wrote: > A ssh connection was closed due to the following error: > > Disconnecting: Bad packet length 3265385124. > > Where does this come from? Is it a bug? Maybe your ssh server only supports ssh version 1 and your client wants to use version

ssh error "Disconnecting: Bad packet length 3265385124."

A ssh connection was closed due to the following error: Disconnecting: Bad packet length 3265385124. Where does this come from? Is it a bug? TIAFAI, -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: - 100% validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat Int

ssh error "Authentication response too long: 1433299822"

SOLVED: I show below both the "ssh" problem that arose and its solution. I upgraded ssh to version 3.4p1-0.0potato1 from within Debian's potato distribution to get the final potato versions and security updates (before I upgrade to woody, and then to sarge, neither of which enters into this probl

[Fwd: Re: ssh error - no controlling tty] SOLVED

I have gotten to the bottom of my issue. It was not ssh it was one of the daemons I am starting out of inittab. It was not sucessfully backgrounding so init never finished. Weird one. As always thankyou for the help. Drew Original Message Subject: Re: ssh error - no

Re: ssh error - no controlling tty

Sean 'Shaleh' Perry wrote: > > On 29-Nov-2000 Andrew Hall wrote: > > Hello, > > > > I have a debian potato system running in a cobalt raq 3. All is working > > 100% > > except ssh. When I > > try to ssh from my box to localhost or anywhere else I get the error "You > > have no controlling tty.

RE: ssh error - no controlling tty

On 29-Nov-2000 Andrew Hall wrote: > Hello, > > I have a debian potato system running in a cobalt raq 3. All is working 100% > except ssh. When I > try to ssh from my box to localhost or anywhere else I get the error "You > have no controlling tty. > Cannot read passphrase" Please remember tha

ssh error - no controlling tty

Hello, I have a debian potato system running in a cobalt raq 3. All is working 100% except ssh. When I try to ssh from my box to localhost or anywhere else I get the error "You have no controlling tty. Cannot read passphrase" Please remember that I do not have a physical /dev/tty1 becuase t

SSH Error

I am trying to set up SSH on my system. I have a normal user account "lint". I do a "ssh -l lint localhost", which results in: > ssh -l lint lint ssh_exchange_identification: read: No such file or directory Any Ideas? Thanks, Bryan