> Okay, I set LogLevel=DEBUG3 and reloaded sshd, but I got no more
> output than usual:
> May 27 09:14:55 treat sshd[11739]: Received SIGHUP; restarting.
> May 27 09:14:55 treat sshd[2352]: Server listening on 0.0.0.0 port 22.
> May 27 09:15:31 treat sshd[2356]: Connection from 64.166.164.53
> port 32776
> May 27 09:15:36 treat sshd[2356]: Accepted keyboard-interactive/pam
> for kevin from 64.166.164.53 port 32776 ssh2
> May 27 09:15:36 treat sshd(pam_unix)[2361]: session opened for user
> kevin by (uid=0)
>
> And when it's "ssh" instead of "scp", I get:
>
> May 27 09:20:53 treat sshd[2392]: Connection from 64.166.164.53
> port 32777
> May 27 09:20:57 treat sshd[2392]: Accepted keyboard-interactive/pam
> for kevin from 64.166.164.53 port 32777 ssh2
> May 27 09:20:57 treat sshd(pam_unix)[2402]: session opened for user
> kevin by (uid=0)
> May 27 09:21:01 treat sshd[2402]: Connection closed by 64.166.164.53
> May 27 09:21:01 treat sshd(pam_unix)[2402]: session closed for user
> kevin
> May 27 09:21:01 treat sshd[2402]: Closing connection to 64.166.164.53
>
> Which covers a simple login-logout sequence.
>
> --
> Kevin O'Gorman, PhD
well, it really looks from both ends like it's working. what is the
shell for the given user? in /etc/passwd, if you're using local
authentication.
That was the hint I needed. It's /bin/bash, which reminded me I just changed something
in .bashrc which outputs a message and does some other stuff which must be
confusing scp. In fact, I just confirmed that by commenting it out. Now scp works too.
So: PROBLEM SOLVED.
Now I just have to figure out how to tailor it some more so the offending code is skipped
for 'scp'. That I can do.
Thanks for the help.
++ kevin
--
Kevin O'Gorman, PhD
