SSH hosed, only rubble remains

On 5/25/06, Kevin O'Gorman <gmail.com"> kogormangmail.com> wrote:

Somewhere along the line, ssh and ssh2 have gotten conflated, confused or just
downright broken.&nbsp; I have been running ssh daemon(s) for so long I don't even
remember how I set them up.  They Just Ran (TM).

For a short while, ssh connections to here (home) from work have taken an
unusually long time to establish.  I thought it was something to do with my
domain registration, which was changing at the same time, but that has settled
down (I think).&nbsp; And I've been too busy surviving a car crash and attendant
medical problems to be exactly on top of the situation.

Now I cannot seem to make a connection at all, and I can't make much sense
out of the setup I have.

First, I have both an
/etc/init.d/sshd

--
Kevin O'Gorman, PhD

On May 25, 2006, at 1:07 PM, Kevin O'Gorman wrote:

&gt; Somewhere along the line, ssh and ssh2 have gotten conflated,
> confused or just
> downright broken.&nbsp; I have been running ssh daemon(s) for so long I
> don't even
> remember how I set them up. &nbsp;They Just Ran (TM).
>
> For a short while, ssh connections to here (home) from work have
> taken an
> unusually long time to establish.  ;I thought it was something to do
> with my
> domain registration, which was changing at the same time, but that
> has settled
&gt; down (I think).&nbsp; And I've been too busy surviving a car crash and
> attendant
> medical problems to be exactly on top of the situation.
>
> Now I cannot seem to make a connection at all, and I can't make
> much sense
> out of the setup I have.
>
> First, I have both an
> /etc/init.d/sshd
>
> --
> Kevin O'Gorman, PhD

hmmm, i imagine you meant there to be more there.&nbsp; if you have
console access to the box, tail -f on the messages log while
attempting to do an ssh -v -v -v ip_address from another client.
that might tell you something.

On 5/26/06, Kevin O'Gorman <gmail.com">kogormangmail.com> wrote:

On 5/25/06, John Jolet <jolet.net" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">johnjolet.net > wrote:

On May 25, 2006, at 1:07 PM, Kevin O'Gorman wrote:

&gt; Somewhere along the line, ssh and ssh2 have gotten conflated,
> confused or just
> downright broken.&nbsp; I have been running ssh daemon(s) for so long I
> don't even
> remember how I set them up. &nbsp;They Just Ran (TM).
>
> For a short while, ssh connections to here (home) from work have
> taken an
> unusually long time to establish.  ;I thought it was something to do
> with my
> domain registration, which was changing at the same time, but that
> has settled
&gt; down (I think).&nbsp; And I've been too busy surviving a car crash and
> attendant
> medical problems to be exactly on top of the situation.
>
> Now I cannot seem to make a connection at all, and I can't make
> much sense
> out of the setup I have.
>
> First, I have both an
> /etc/init.d/sshd
>
> --
> Kevin O'Gorman, PhD

hmmm, i imagine you meant there to be more there.&nbsp; if you have
console access to the box, tail -f on the messages log while
attempting to do an ssh -v -v -v ip_address from another client.
that might tell you something.

Yeh.&nbsp; Fumblefingers sent it on its way before it was ready.&nbsp; You got
the gist though, it seems.

Anyway, I tried what you asked (fortunately I have multiple hosts here).
The ssh -v -v -v brokenhost command produces a raft of info. ; Below I included
just what's after entering the password, but I doubt it will help. ; I need
to get the daemon to be similarly prolix.&nbsp; This host fails to complete
ssh requests from all comers -- Windows running SSH Secure Shell
or Linux or Solaris running whatever ssh they have, so I need the
info from this gentoo server.

So how do I get that?

Password:
debug1: packet_send2: adding 32 (len 25 padlen 7 extra_pad 64)
debug2: input_userauth_info_req
debug2: input_userauth_info_req: num_prompts 0
debug1: packet_send2: adding 48 (len 10 padlen 6 extra_pad 64)
debug1: ssh-userauth2 successful: method keyboard-interactive
debug3: clear hostkey 0
debug3: clear hostkey 1
debug3: clear hostkey 2
debug1: fd 4 setting O_NONBLOCK
debug1: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug1: send channel open 0
debug1: Entering interactive session.
debug2: callback start
debug1: ssh_session2_setup: id 0
debug1: Sending command: scp -v -t .
debug1: channel request 0: exec
debug2: callback done
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072

++ kevin

> Password:
> debug1: packet_send2: adding 32 (len 25 padlen 7 extra_pad 64)
> debug2: input_userauth_info_req
> debug2: input_userauth_info_req: num_prompts 0
> debug1: packet_send2: adding 48 (len 10 padlen 6 extra_pad 64)
> debug1: ssh-userauth2 successful: method keyboard-interactive
> debug3: clear hostkey 0
> debug3: clear hostkey 1
> debug3: clear hostkey 2
> debug1: fd 4 setting O_NONBLOCK
> debug1: fd 5 setting O_NONBLOCK
> debug1: channel 0: new [client-session]
> debug3: ssh_session2_open: channel_new: 0
> debug1: send channel open 0
> debug1: Entering interactive session.
&gt; debug2: callback start
> debug1: ssh_session2_setup: id 0
> debug1: Sending command: scp -v -t .
> debug1: channel request 0: exec
> debug2: callback done
> debug1: channel 0: open confirm rwindow 0 rmax 32768
> debug2: channel 0: rcvd adjust 131072
okay, so in this instance, you're trying an scp...what happens when
you do an ssh?  and does anything at all show up in the logs on the
server? &nbsp;In the /etc/ssh/sshd_config file, there can be a LogLevel
entry.  try DEBUG2 or DEBUG3
--
gentoo.org">gentoo-usergentoo.org mailing list

> 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)
&gt;
> And when it's "ssh&quot; instead of "scp&quot;, 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)
&gt; 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.&nbsp; what is the
shell for the given user? ; in /etc/passwd, if you're using local
authentication.

>
> That was the hint I needed.&nbsp; 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.
&gt;
> Now I just have to figure out how to tailor it some more so the
> offending code is skipped
&gt; for 'scp'.&nbsp; That I can do.
>

bash has a built-in variable that tells you what the command
was....should be able to test for "scp&quot; in your script....  ;i've
never tried to get that fancy with .bashrc.
--
gentoo.org"> gentoo-usergentoo.org mailing list

That does not work for ssh/scp sessions.&nbsp; I usually test $PS1 to tell
> if it's really a shell -- the variable does not even exist for an
> scp session,
&gt; although .bashrc gets called.
can you give us an example of what your .bashrc looks like?

On May 28, 2006, at 11:21 AM, Kevin O'Gorman wrote:

&gt; On 5/27/06, John Jolet <jolet.net">johnjolet.net> wrote:
>; That does not work for ssh/scp sessions.&nbsp; I usually test $PS1 to tell
> > if it's really a shell -- the variable does not even exist for an
> > scp session,
&gt; > although .bashrc gets called.
&gt; can you give us an example of what your .bashrc looks like?
>
> Well, the whole thing is kinda long, but the part I was fooling
&gt; with lately
>; now looks like this, and partly automates the use of ssh-agent for my
> (very frequent) use of ssh from home to some machines at work. ; The
> problem was probably either the "echo" commands or that this actually
&gt; proceeds within a subshell.
>
>
&gt; if [ "x&quot; != "x$PS1" ] ; then
>&nbsp;   ; SHELL_LOGIN=1
> else
>&nbsp;   ; # Probably scp; empty string is false
>  ; &nbsp; SHELL_LOGIN=
> fi
>
&gt; if [ -n "$SHELL_LOGIN&quot; ]
> then
>&nbsp;   ; if [ -z "$SSH_AGENT_PID&quot; ]
>&nbsp; &nbsp;  then
>  ; &nbsp; &nbsp; &nbsp; # not yet running in ssh-agent
> &nbsp;   ; &nbsp;  ssh-agent /bin/bash
> &nbsp;   ; &nbsp;  r=$?
>&nbsp;   ; &nbsp; &nbsp; echo Done with ssh-agent
> &nbsp;   ; &nbsp;  sleep 1
>&nbsp; &nbsp; &nbsp; &nbsp;  exit $r
>&nbsp; &nbsp;  else
>&nbsp;   ; &nbsp; &nbsp; # this is an ssh-agent subshell
> &nbsp;   ; &nbsp;  echo You may want to run ssh-add.
&gt; &nbsp; &nbsp; fi
> fi
>
&gt; --
> Kevin O'Gorman, PhD

well, you could comment out the "echo" commands and try it.
personally, I try to stay away from things happening automatically
for me. &nbsp;just my preference. &nbsp;I would rename .bashrc to something
else, like old.bashrc and do the scp and see if that works.
depending on what your needs are, you could also add a second user
with the same uid, but a different home directory and use that other
user for scp..... shrug.&nbsp; not a big fan of ssh_agent (or anything
that caches credentials).