This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Cannot SSH in to server
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Pat Lightbody <plightbo at cisco dot com>
- Cc: cygwin at cygwin dot com
- Date: Thu, 1 May 2003 13:22:58 -0400 (EDT)
- Subject: Re: Cannot SSH in to server
- Reply-to: cygwin at cygwin dot com
On Thu, 1 May 2003, Pat Lightbody wrote:
> I have a very strange problem: whenever I have an xterm window launced from
> whithin XFree86 (note: this is different than run xterm from startx.bat), I
> cannot SSH in to any server unless I can use my RSA/DSA keys (ie, if it asks
> me for a normal password, my ssh client locks up). I'm sure it has something
> to do with my env variables, so I've attached the output of 'set' for the
> xterm that does work and the ones that don't. Also, attached is the debug
> level logs of the ssh client when it locks up. Anyone have any ideas?
>
> -Pat
Pat,
Did you do a diff on the two set outputs? Here are some relevant
sections (not in the original order, with some annotations):
6c5
< BASH=/usr/bin/bash
---
> BASH=/bin/bash
36a36,37
> MAKE_MODE=unix
> MANPATH=:/usr/ssl/man
44c45
< PATH='.:/usr/bin:/usr/X11R6/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/SecureCRT/:/cygdrive/c/jdk1.4.1/bin:/usr/bin:/usr/local/bin:/cygdrive/c/jdk1.4.1/maven/bin:/cygdrive/c/jdk1.4.1/ant/bin:/cygdrive/c/jdk1.4.1/maven/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/SecureCRT/'
---
> PATH='/usr/local/bin:/usr/bin:/bin:.:/usr/bin:/usr/X11R6/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/SecureCRT/:/cygdrive/c/jdk1.4.1/bin:/usr/bin:/usr/local/bin:/cygdrive/c/jdk1.4.1/maven/bin:/cygdrive/c/jdk1.4.1/ant/bin:/cygdrive/c/jdk1.4.1/maven/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/SecureCRT/'
66a70
> TZ=PST8PDT7,M4.1.0/2,M10.5.0/2
67a72
> USER=plightbo
The above all seem to indicate that the working bash wasn't run with the
--login option (i.e., /etc/profile wasn't executed), whereas the hanging
bash was (it could also be that the non-working xterm had a "-ls" option).
However, I suspect the above is largely irrelevant, and your problem lies
here:
61a63,64
> SSH_AGENT_PID=612
> SSH_AUTH_SOCK=/tmp/ssh-DBwS1292/agent.1292
You have ssh-agent running in the non-working bash. I'm guessing it has
something to do with your problem. "man ssh-agent" for details.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Knowledge is an unending adventure at the edge of uncertainty.
-- Leto II
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/