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/

Attachment: signature.asc
Description: Digital signature

Reply via email to