New issue 58 by tmcreech: Hangs when SSH-ing into Solaris shells after login
http://code.google.com/p/shellinabox/issues/detail?id=58
What steps will reproduce the problem?
1. Get shellinabox hosted on a Linux box
2. Log in to that machine using shellinabox
3. ssh somesolarisbox.com, authenticate
What is the expected output? What do you see instead?
I expect to see bash/zsh/whatever on the Solaris box. Instead, the
tab/window in my browser seems to stop responding key presses.
What version of the product are you using? On what operating system?
2.10-1 on Debian Lenny (i386) from the .deb provided at code.google.com.
Please provide any additional information below.
I have tried connecting to Solaris 10 and Opensolaris snv111 and snv133
machines using FireFox 3.5, 3.6, Opera 10.10, and Safari 4.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
I can also confirm this problem with multiple different systems.
Also Shell in a box will not build on Solaris. So shell in a box will not
work in anyway with solaris.
Maybe it's related to termcap/terminfo and how it's processed by BSD and
Solaris? I know a lot of older systems complain about something as common
as TERM=rxvt-unicode, so maybe changing the value of shellinabox's $TERM
would fix it?
After connection from Linux (OEL6) to Solaris (11) and no output is given,
the commands are processed!
When you issue 'exit' right after login to Solaris, the output
is 'Connection to w.x.y.z closed.' (probably more will work to...)
SSH-ing with putty from Linux to Solaris works, so it seems only the
processing off output from Solaris.
Has there been any movement on this bug?
I can confirm this bug exists with Shellinabox running on Debian 6 and
CentOS 6 when connecting to a Solaris 10 host. Problem exists if the
shellinabox service is LOGIN or SSH.
Additionally, if Shellinabox is configured to SSH directly to a Solaris
host, ala -s /:SSH:solaris.host.net it also fails. (same behaviour as if
logging into a Linux host and then ssh'ing to the Solaris host)
From my investigations I think it may be todo with the way Shellinabox does
STDIN/STDOUT redirection. But I havent looked too deeply at the source code.
Further, telnet to a Solaris 11 host works fine.
Further. Running a telnet server on the Linux based Shellinabox server, and
telnetting to localhost then SSH'ing to a Solaris host works fine.
As a stop gap, anyone else experiencing this bug may try this if your local
security policy allows it:
Run a telnet server on localhost
Setup shellinabox to run telnet localhost as an unprivileged user rather
than /bin/login
We use this work-around to make it works
- run shellinaboxd, putting a script that make a remote connection as first
task to do
- when an user call shellinabox, that script makes a telnet connection on
localhost
- then, using expect (bash scripting on *unix), the script makes a ssh
connection on Solaris remote host
I hope this information could help someone (this problem make us crazy)