In comp.sys.raspberry-pi, Jack Fearnley   wrote:
> On Thu, 14 Dec 2017 17:55:13 +0000, Roger Bell_West wrote:
> >>I enter the password and the terminal freezes.
> >>Any suggestions?
> > Look at the sshd logs on the target host. /var/log/auth.log is the main
> > one, though there may be some useful content in daemon.log too.
>
> The following list from /var/log/auth.log shows me starting sshd with
> 'sudo service start sshd' and attempting to connect with 'ssh
> pi@192.168.0.104'
>
> *************************************************************************
> Dec 14 13:14:33 beta sshd[5635]: Accepted password for jack from
> 192.168.0.104 port 56346 ssh2
> Dec 14 13:14:33 beta sshd[5635]: pam_unix(sshd:session): session opened
> for user jack by (uid=0)
> Dec 14 13:14:33 beta systemd-logind[768]: New session 8 of user jack.
> Dec 14 13:17:01 beta CRON[5727]: pam_unix(cron:session): session opened
> for user root by (uid=0)
> Dec 14 13:17:01 beta CRON[5727]: pam_unix(cron:session): session closed
> for user root
> ************************************************************************

Nothing in there for user pi.

I have two suggestions:

  1) Use ssh with -v or -v -v -v to get an idea of what ssh thinks is
     going on.

  1b) Start a verbose instance of sshd on a different port, and look at
      it's verbose logs (can be a little trickier, because you need key
      files, but you can do this as a non-root user).

  2) The ssh is working, but you have configured something on startup
     (eg in .login or .profile) that prevents a shell from ever
     answering. Something like 'startx' in your .login, for example.

Elijah
------
usually can figure these problems out without resorting to a 1b solution

--- SoupGate-Win32 v1.05