[lug] mixing linux/win cvs/ssh

[D. Stimits]

Glenn Murray wrote:
> 
> I know of no way to use ssh without placing keys, perhaps someone else
> can help.

I was thinking of password logins. I.E., it asks for a password based on
the regular user account name/pass, since no keys (or at least matching)
exist.

> 
> I have seen the "stdin: is not a tty" message a lot, too, but I have
> no idea what it means.

I get this even with a direct ssh login. Perhaps because remote logins
are pty (pseudo terminal) rather than regular tty. This would also mean
an X11 login locally should do so. I've never had a problem with it, at
least not with anything I know of. I have found that if the login script
for the login shell, maybe a welcome message, will break scp and
possibly other ssh applications. On the other hand, I thought it might
offer a clue, despite my not knowing of a specific case where "is not a
tty" causes failure.

> 
> Thanks for the compliment though, perhaps I'll get motivated to update
> the page.

It is useful, especially because it brings together information.

D. Stimits, stimits at idcomm.com

> 
> Glenn Murray
> www.mines.edu/~gmurray/public_html/Welcome.html
> 
> On Wed, 3 Oct 2001, D. Stimits wrote:
> 
> > In general, I do get a message during ssh cvs checkouts:
> > stdin: is not a tty
> >
> > This does not appear to be a problem. At least not on command line. I am
> > able to check out files over cvs this way from either win or linux
> > (server is linux). What fails are all of the gui interfaces (win only).
> > I'm thinking maybe the "stdin: is not a tty" is interfering. For
> > example, scp will fail if some startup file in the home directory echoes
> > something like "welcome".
> >
> > In general, the web page below is quite helpful. But it doesn't tell me
> > one thing I need to know. It seems to rely on placing keys and not using
> > passwords. Is it possible that the password interactive is not possible
> > with ssh cvs on the win gui? I do get the password prompt, but then it
> > fails. Although I don't want a key pair that requires an rsa password
> > each time, I *do* want it to prompt for my login pass on the remote
> > machine. I'm thinking the gui's are too limited to do this, and even
> > though it prompts for pass, it is causing failure.
> >
> > Also, my login shell is tcsh, so I'd have to find some equivalent to
> > that case below if it is mandatory to work around non-interactive
> > logins. Before I can do more testing though, I'll have to uninstall some
> > of the tcl stuff I have now, it lacks tk, and probably isn't good to mix
> > versions.
> >
> > D. Stimits, stimits at idcomm.com
> >
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug