
10-21-2008, 01:47 PM
|
| Junior Member | | Join Date: Sep 2009
Posts: 0
| |
SSH client insists on /dev/tty Hi,
I'm running a RHEL 5.2 on an IBM System z Mainframe. From this system, I
created a RAM disk with some necessary binaries and my own init script.
I now can boot into this RAM disk using the distribution kernel [1].
There are two ways to connect to this system running with my RAM disk:
Directly with a x3270 terminal [2] or via SSH to the SSH server,
running within this RAM disk. The problem is that SSH [3] is not
working when I use the x3270 client.
If I try to SSH to another machine from within the RAM disk, SSH will
say:
debug1: read_passphrase: can't open /dev/tty: No such device or address
Host key verification failed.
Obviously, /dev/tty *does* exist and has the proper permissions:
sh-3.2# ls -l /dev/tty
crw-rw-rw- 1 sysload 0 5, 0 Oct 21 15:01 /dev/tty
The shell running in this terminal is using /dev/console, although ps
doesn't seem to get this right:
sh-3.2# ps
PID TTY TIME CMD
717 ? 00:00:00 sh
sh-3.2# ls -l /proc/717/fd
total 0
lrwx------ 1 sysload 0 64 Oct 21 15:01 0 -> /dev/console
lrwx------ 1 sysload 0 64 Oct 21 15:05 1 -> /dev/console
lrwx------ 1 sysload 0 64 Oct 21 15:05 2 -> /dev/console
lrwx------ 1 sysload 0 64 Oct 21 15:05 255 -> /dev/console
[..]
If I connect via SSH from my client, the shell running within this
session is using pts/0. Now, I *can* SSH to another machine, since SSH
is now able to ask for a password.
The problem is, that I need SSH to work without this, because there are
scripts that need to be run. But I can't figure out how to tell SSH
which device to use. The -t option doesn't do the trick.
Since I have no idea on what to do next, any hint would be greatly
appreciated.
thanks in advance,
stephan
[1] In this case 2.6.18-92.el5
[2] That's like a serial terminal, for those not familiar with System z
[3] OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006 |