putty lock up connecting to ssh_sshd

Lennart Ohman <>
Sat Feb 18 17:48:53 CET 2006


Hi,
I have been experimenting with Putty too and found it not
to work well (not at all) with the erlang ssh server.
The main reasons seems to be that the putty terminal identifies
it self as version 1.99 which should mean version 1 or 2 if I
am not mistaken. But the server does not handle this. The
responsible person in the OTP team is notified.

/Lennart

-------------------------------------------------------------
Lennart Ohman                   office  : +46-8-587 623 27
Sjoland & Thyselius Telecom AB  cellular: +46-70-552 67 35
Sehlstedtsgatan 6               fax     : +46-8-667 82 30
SE-115 28, STOCKHOLM, SWEDEN    email   : 
> -----Original Message-----
> From:  [mailto:owner-erlang-
> ] On Behalf Of Serge Aleynikov
> Sent: Saturday, February 18, 2006 3:43 PM
> To: ke.han
> Cc: erlang-questions
> Subject: Re: putty lock up connecting to ssh_sshd
> 
> Do you have the HOME environment variable set?  If not do set it to
> point to some existing directory, before starting an SSH server.
> 
> See if this helps.
> 
> Serge
> 
> ke.han wrote:
> > I am starting ssh_sshd on a freebsd 6 server running erlang (starting
> > from yaws).
> >
> > 1> ssh_sshd:listen(3322, [{user_passwords, [{"admin","admin"}]}]).
> > {ok,<0.33.0>}
> >
> > I then go to my windows client and run putty, connecting to port 3322 on
> > the appropriate ip.
> > I receive the username and admin prompts to which I respectively reply
> > admin and admin.
> > My terminal responds by showing my the erlang shell as expected but then
> > putty accepts no further input.  Its simply locked up.
> >
> > The erlang server does not show any errors (until I close putty and get
> > a disconnect).
> >
> > I have also tried to log in from a windows erlang shell with:
> >
> > ssh_ssh:connect("192.168.1.4", 3322, []).
> >
> >
> > This first asks me if I want to accept the host address to which I reply
> > "y". Then I get the following error on my erlang windows shell:
> >
> > ** exited: {error,enoent} **
> >
> >
> > again, no errors on the server shell.
> > If I do the same thing with the server name mapping instead of the ip, I
> > get the same results.
> >
> > Anyone else experience this?
> > thanks, ke han
> >






More information about the erlang-questions mailing list