DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just upgraded two Debian Etch/Sid systems the day before yesterday. Afterwards, I can no longer use ssh for remote login from one to the other. ssh was not upgraded, but some other packages were (including libc6 from sid). Now when I try a remote login, I get a message saying the connection is closed by the server. Here are the last lines of the debugging output from "ssh -vvv matt@192.168.0.101":
Code:
debug3: authmethod_lookup keyboard-interactive
debug3: remaining preferred: password
debug3: authmethod_is_enabled keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
Connection closed by 192.168.0.101
I have tried searching Debian bug reports, but I can't find anything. Any ideas?
Thanks for the advice. Somehow, I didn't need to try it. Yesterday and today I ran apt-get dist-upgrade on both systems and ssh is working again. I do not know what was broken or what was fixed, but everything is working now.
One of lifes little mysteries then.
PS: just read on another forum that a dist-upgrade had borked some file permissions under /tmp and stopped ssh among other stuff. But if it works, good.
PPS: if you're running sid with kde you might want to be a bit careful dist-upgrading ATM: http://lists.debian.org/debian-kde/2.../msg00089.html
in the beggining i tried to downgrade to ssh-stable.
No success
I figured out that was a glibc problem. So i tried to downgrade glibc. No success again.
The third attempt was to downgrade the whole systems to stable. At this point dpkg stopped in the middle of the downgrade (dependencies hell) . It left behind a mixed system with dpkg crashed & ssh not staring at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.