need help: keyboard-interactive authentification of ssh stopped working
Hi, during the last one or two weeks, suddenly I lost the ability to log into one of my machines using ssh. It seems that the keyboard-interactive authentification mechanism suddenly stopped working. I am a bit of a loss how to track this down, any help would be greatly appreciated. The details: * The machine runs a current version of the stable distribution of Debian, together with a few packages from debian-volatile. The installed version of ssh is 3.8.1p1-8.sarge.4 . * I reported bug #364635 about this. The bug report contains the full output for both client and server, as well as my configuration file. See http://bugs.debian.org/364635 . * The problem also occurs when doing ssh localhost. Client and server manage to communicate with each other. The last message on the client side is debug1: Next authentication method: keyboard-interactive debug2: userauth_kbdint debug2: we sent a keyboard-interactive packet, wait for reply Connection closed by 127.0.0.1 The last messages on the server side are Apr 24 16:50:42 seehuhn sshd[26029]: debug3: mm_request_receive entering Apr 24 16:50:42 seehuhn sshd[26029]: debug3: monitor_read: checking request 48 Apr 24 16:50:42 seehuhn sshd[26029]: debug3: mm_answer_pam_init_ctx Apr 24 16:50:42 seehuhn sshd[26029]: debug3: PAM: sshpam_init_ctx entering Except for the Connection closed, neither client nor server seem to emit any error messages. * Logging in remotely worked until a few days ago. I cannot remember any changes which should have affected ssh. The most recent package updates where [UPGRADE] exim4 4.50-8 - 4.50-8sarge2 [UPGRADE] exim4-base 4.50-8 - 4.50-8sarge2 [UPGRADE] exim4-config 4.50-8 - 4.50-8sarge2 [UPGRADE] exim4-daemon-light 4.50-8 - 4.50-8sarge2 [UPGRADE] libc6 2.3.2.ds1-22 - 2.3.2.ds1-22sarge3 [UPGRADE] libc6-dev 2.3.2.ds1-22 - 2.3.2.ds1-22sarge3 [UPGRADE] libperl5.8 5.8.4-8sarge3 - 5.8.4-8sarge4 [UPGRADE] locales 2.3.2.ds1-22 - 2.3.2.ds1-22sarge3 [UPGRADE] mutt 1.5.9-2 - 1.5.9-2sarge1 [UPGRADE] perl 5.8.4-8sarge3 - 5.8.4-8sarge4 [UPGRADE] perl-base 5.8.4-8sarge3 - 5.8.4-8sarge4 [UPGRADE] perl-doc 5.8.4-8sarge3 - 5.8.4-8sarge4 [UPGRADE] perl-modules 5.8.4-8sarge3 - 5.8.4-8sarge4 [UPGRADE] tar 1.14-2.1 - 1.14-2.2 which looks harmless to me. * Luckily, public key based authentification still works. Any help in tracking this down would be most welcome. If you need more information, please let me know. Many thanks, Jochen PS.: please Cc: me on replies, I am not subscribed to debian-user. -- http://seehuhn.de/ signature.asc Description: Digital signature
ssh stopped working
I had ssh working fine on my debian server running woody. I changed the password of the root user and restarted the machine and am now unable to locally or remotely connect using ssh clients. If I start ssh in debug mode with ssh d it will connect with client tools. I am not getting any messages in /var/log/messages relating to failed connections. I also tried to regenerate the key with sshkeygen t rsa f The command completed successfully, however I am still unable to connect. I have verified hosts.allow and hosts.deny and they are both correct. I have tried changing the password back to the original one and restarting. I tried changing the listening port to 222 and it would still not connect. I have searched google, but am unable to find anything that will help. Thanks in advance for your suggestions.
Re: ssh stopped working
On Thu, Jan 22, 2004 at 06:42:23PM -0600, Michael Martinell wrote: I changed the password of the root user and restarted the machine and am now unable to locally or remotely connect using ssh clients. snip (0) Perhaps the restart of your machine was what was the cause: maybe you configured the running system, but didn't alter the configfiles? (1) See if sshd is really listening there: netstat -a; nc localhost ssh (2) Are you sure you looked in the appropriate logfile? The default one is /var/log/auth.log (3) Sniff on the connection using tcpdump(8) or friends (4) Maybe it's not the server, but the client where the problem lies? (5) Debugging both sshd ssh with strace(1), you can get a really detailed picture of what's going on; combine with (3). HTH, Jan. -- Jan Minar Please don't CC me, I'm subscribed. x 9 pgp0.pgp Description: PGP signature
Re: ssh stopped working
On Friday 23 January 2004 01:42, Michael Martinell wrote: I changed the password of the root user and restarted the machine and am now unable to locally or remotely connect using ssh clients. Did you use any non-ascii characters in your new root password? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: ssh stopped working
-Original Message- From: Jan Minar [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 7:11 PM To: [EMAIL PROTECTED] Subject: Re: ssh stopped working On Thu, Jan 22, 2004 at 06:42:23PM -0600, Michael Martinell wrote: I changed the password of the root user and restarted the machine and am now unable to locally or remotely connect using ssh clients. snip (0) Perhaps the restart of your machine was what was the cause: maybe you configured the running system, but didn't alter the configfiles? (1) See if sshd is really listening there: netstat -a; nc localhost ssh (2) Are you sure you looked in the appropriate logfile? The default one is /var/log/auth.log (3) Sniff on the connection using tcpdump(8) or friends (4) Maybe it's not the server, but the client where the problem lies? (5) Debugging both sshd ssh with strace(1), you can get a really detailed picture of what's going on; combine with (3). HTH, Jan. -- Jan Minar Please don't CC me, I'm subscribed. x 9 (0) I have restarted the machine several times before without a problem. I have actually not worried much about the server side of ssh since I installed it, and the installer set it up. (1) ssh was not listening, Even when I run sshd -d I don't see anything. On another machine where ssh words, I see the expected output, so I know I typed it in correctly. (2) I tail -f this logfile. The only time it came up with a new entry was when the connection was successful during the sshd -d This entry stated that the connection was successful for root. (3) I used tcpdump and saw the ssh request being made by my client computer. Since ssh wasn't actually listening it did not respond. When in debug mode I also saw the ssh connection. (4) I can connect in debug mode. (5) I did the strace, and it is very detailed. I compared it to a strace from another machine where ssh works, and I don't see any significant differences. Is there anything I should be looking at specifically? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: ssh stopped working
-Original Message- From: Henning Moll [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 7:14 PM To: [EMAIL PROTECTED] Subject: Re: ssh stopped working On Friday 23 January 2004 01:42, Michael Martinell wrote: I changed the password of the root user and restarted the machine and am now unable to locally or remotely connect using ssh clients. Did you use any non-ascii characters in your new root password? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I used a combination that contained: ! @ The rest were letters and numbers, starting with a letter. No non-standard alt + characters were used. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSH stopped working
is there a sshd (the server daemon) runing at the other side? Are you sure? Thank you for the reply. Yes, I am sure sshd is running on the other side. Other computers can use ssh to attach to the machine. Randy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSH stopped working
Em 25 Jun 2002 05:26:32 -0700 Randolph S. Kahle [EMAIL PROTECTED], conhecido dependente de drogas (Coke e BigMac's), wrote: Thank you for the reply. Yes, I am sure sshd is running on the other side. Other computers can use ssh to attach to the machine. Randy well.. Maybe you have an know_hosts key at that machine (or here). If you can, ask people there to remove/erase/destroy your $HOME/.ssh contents. Then, try again. Also, it is appropriate to have somebody there looking at the /var/log/messages for occurencies when you try to connect. As I am not joined to the debian list, think that it is proper to cc to me. --- saudações, irado furioso com tudo Linux User 179402 mais crimes são cometidos em nome das religiões do que em nome do ateísmo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SSH stopped working
I have been using SSH for a long time in my network (local network, through firwalls, into other supported networks, etc) without problems. Recently, I found that I cannot get a connection with some remote machines. When I try to make a connection, I get the following error: ssh_exchange-identifiaction: Connection closed by remote host When I try with debuging on: ssh -v -v -v host It appears to die just when the SSH protocol negotiation is starting (1.0/1.5/2.0). My hosts are all either Woody or Potato (with 2.4 kernel upgrade). Any tips would be appreciated! Randy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSH stopped working
Em 04 Jun 2002 11:01:54 -0700 Randolph S. Kahle [EMAIL PROTECTED], conhecido dependente de drogas (Coke e BigMac's), wrote: ssh_exchange-identifiaction: Connection closed by remote host When I try with debuging on: ssh -v -v -v host is there a sshd (the server daemon) runing at the other side? Are you sure? -- saudações, irado furioso com tudo Linux User 179402 mais crimes são cometidos em nome das religiões do que em nome do ateísmo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSH stopped working
ssh_exchange-identifiaction: Connection closed by remote host It appears to die just when the SSH protocol negotiation is starting (1.0/1.5/2.0). do you have an old ssh version? just protocol v1? try to specify the protocol with -1 or -2. some server don't allow access to v1.x anymore. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SSH stopped working
is there a sshd (the server daemon) runing at the other side? Are you sure? Yes, I am sure that it is running. Connections can be made from other machines to that server. Thanks -- Randy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ssh stopped working
Sorry for my quite unprofessional posting. The problem has been solved now; my ISP's dialin-server had a wrong configuration. Andre Berger [EMAIL PROTECTED] writes: Ron Rademaker [EMAIL PROTECTED] writes: Can you take a look at the syslog of the other host??? Maybe that gives you some more information. Ron Rademaker On Sat, 27 May 2000, Andre Berger wrote: I had a functional ssh (potato/ppc), but now it has stopped working. The error message I get is ssh_exchange_identification: Connection closed by remote host when I try to connect to the same hosts as before. I have no idea why. (ssh is already purged and reinstalled.)
ssh stopped working
I had a functional ssh (potato/ppc), but now it has stopped working. The error message I get is ssh_exchange_identification: Connection closed by remote host when I try to connect to the same hosts as before. I have no idea why. (ssh is already purged and reinstalled.) -- Andre
Re: ssh stopped working
Can you take a look at the syslog of the other host??? Maybe that gives you some more information. Ron Rademaker On Sat, 27 May 2000, Andre Berger wrote: I had a functional ssh (potato/ppc), but now it has stopped working. The error message I get is ssh_exchange_identification: Connection closed by remote host when I try to connect to the same hosts as before. I have no idea why. (ssh is already purged and reinstalled.) -- Andre -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
ssh stopped working today
Any help on this will be greatly appreciated! This morning when I tried to use ssh to log into my debian firewall from the private network I get no response. But I can telnet to my isp's server and then ssh back into the debian firewall from there with no problem. I have been ssh'ing into the firewall from the private network for months with no problem. What could have changed? I have changed no settings, and there is no evidence of a break-in (that I can see). It seems strange that I can log in from the public side of the firewall, but not the private side. What could have changed? -Ben Messigner This mail was sent from a 100% Microsoft-free (aka GPF-free) environment. Have a stable day. Use Linux.
update: ssh stopped working
If you read my last post you know that ssh started acting up on my firewall. I could log in from the public side, but got no responce from the private side. In the last hour it has mysteriously started working again. I made no system changes at all -- it just fixed it's self. Does anyone know what's up with this? It was 100% reliable for months - today is the first time there has been a problem. -Ben Messinger This mail was sent from a 100% Microsoft-free (aka GPF-free) environment. Have a stable day. Use Linux.
