This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: ssh2 in xterm problem
- From: "Harold Hunt" <huntharo at msu dot edu>
- To: "Hans Werner Strube" <strube at physik3 dot gwdg dot de>
- Cc: "cygx" <cygwin-xfree at cygwin dot com>
- Date: Thu, 14 Mar 2002 12:21:56 -0500
- Subject: RE: ssh2 in xterm problem
Hans,
Don't forget to cc the list in all replies.
Harold
> -----Original Message-----
> From: Hans Werner Strube [mailto:strube@physik3.gwdg.de]
> Sent: Thursday, March 14, 2002 12:19 PM
> To: huntharo@msu.edu
> Subject: RE: ssh2 in xterm problem
>
>
> > That sounds like normal behavior for Windows applications.
> ssh2 would have
> > to be *specifically* designed in order to be usable from an xterm in
> > Cygwin/XFree86. The reason that it runs in a Cygwin shell is that the
> > Cygwin shell is actually an MS command prompt that is running
> bash... but
> > the xterm is not an instance of an MS command prompt, so ssh2 no longer
> > runs.
> >
> > I hope that makes sense.
>
> This sounds plausible. But "ssh2 no longer runs" is not true, it runs but
> outputs its prompt to the Cygwin shell and can be killed by ^C in
> the xterm
> shell. But why can it write to the Cygwin shell but not read the password
> from there?
>
> (BTW, as an easy workaround I can set the DISPLAY environment in
> the Cygwin
> shell and call ssh2 from there. Remote X clients then appear in the Cygwin
> X window.)