From owner-freebsd-questions  Mon Jan 15 11:36:17 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108])
	by hub.freebsd.org (Postfix) with ESMTP id 6E66537B401
	for <questions@freebsd.org>; Mon, 15 Jan 2001 11:35:59 -0800 (PST)
Received: from ufl.edu (neti.eng.ufl.edu [128.227.235.15])
	by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id OAA165524;
	Mon, 15 Jan 2001 14:35:52 -0500
Message-ID: <3A635154.D55B25C7@ufl.edu>
Date: Mon, 15 Jan 2001 14:36:52 -0500
From: Bob Johnson <bobj@ufl.edu>
X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-STABLE i386)
X-Accept-Language: en, eo
MIME-Version: 1.0
To: danny@vkpc.com
Cc: questions@freebsd.org
Subject: Re: Can't SSH into my computer after update
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> Date: Sun, 14 Jan 2001 04:14:19 -0800
> From: "Danny Yoo" <danny@vkpc.com>
> Subject: Can't SSH into my computer after update
> 
> Hi all,
> 
> I can't seem to SSH into my box now that I've upgraded from 4.1 to 4.2. All
> my config files seem to be in order. What happens is that as soon as I type
> in my password, the connection gets closed. I can log in from the console
> fine though. I'm not really sure what to look at after the upgrade.
> 

If you upgraded to 4.2-STABLE, some of the SSH stuff recently changed.  
One thing that has bit people is that /etc/pam.conf now should have 
an entry for sshd, or you won't be able to log in with ssh, i.e.:

 # OpenSSH with PAM support requires similar modules.  The session one is
 # a bit strange, though...
 sshd    auth    sufficient      pam_skey.so
 sshd    auth    required        pam_unix.so                     try_first_pass
 sshd    session required        pam_permit.so
 
If this is your problem, you probably need to run mergemaster to update 
some of your other configuration files.
 
> The error message looks like:
> 
> debug: authentications that can continue: publickey,password
> debug: next auth method to try is publickey
> debug: key does not exist: /home/userid/.ssh/id_dsa
> debug: next auth method to try is password
> userid@host.com's password:
> debug: ssh-userauth2 successfull: method password
> debug: channel 0: new [client-session]
> debug: send channel open 0
> debug: Entering interactive session.
> debug: client_init id 0 arg 0
> debug: Requesting X11 forwarding with authentication spoofing.
> debug: channel request 0: shell
> debug: channel 0: open confirm rwindow 0 rmax 16384
> Connection to host.com closed by remote host.
> Connection to host.com closed.
> debug: Transferred: stdin 0, stdout 0, stderr 87 bytes in 0.2 seconds
> debug: Bytes per second: stdin 0.0, stdout 0.0, stderr 522.8
> debug: Exit status -1
> debug: writing PRNG seed to file /home/userid/.ssh/prng_seed

Did these come from the client or the server (looks like client to me)? 
Error info from the server would probably be useful.

- Bob

> 
> It's all actually overwhelming since I don't know where to start in terms of
> knowing what happened when I updated all my sources and built the world and
> what not. Could someone explain what happened and offer any possible reasons
> why SSH refuses all connections?
> 
> Thanks,
> 
> Danny
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message