Re: New world - about 2 days old - SSH broken?

From: Kostik Belousov <kostikbel_at_gmail.com>
Date: Thu, 5 Jul 2007 15:51:24 +0300
On Thu, Jul 05, 2007 at 02:35:43PM +0200, Ed Schouten wrote:
> Hello,
> 
> About two days ago I started a buildworld on my SPARC64 (only a Sun
> U10). This morning the compilation was finished, so I installed a new
> world and kernel. The result:
> 
> | $ ssh -v ultra
> | OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.8e 23 Feb 2007
> | debug1: Reading configuration data /home/ed/.ssh/config
> | debug1: Reading configuration data /etc/ssh/ssh_config
> | debug1: Connecting to ultra.fxq.nl [2001:7b8:310::1] port 22.
> | debug1: Connection established.
> | debug1: identity file /home/ed/.ssh/identity type -1
> | debug1: identity file /home/ed/.ssh/id_rsa type 1
> | debug1: identity file /home/ed/.ssh/id_dsa type -1
> | debug1: Remote protocol version 2.0, remote software version OpenSSH_4.5p1 FreeBSD-20061110
> | debug1: match: OpenSSH_4.5p1 FreeBSD-20061110 pat OpenSSH*
> | debug1: Enabling compatibility mode for protocol 2.0
> | debug1: Local version string SSH-2.0-OpenSSH_4.5p1 FreeBSD-20061110
> | debug1: SSH2_MSG_KEXINIT sent
> | debug1: SSH2_MSG_KEXINIT received
> | debug1: kex: server->client aes128-cbc hmac-md5 none
> | debug1: kex: client->server aes128-cbc hmac-md5 none
> | debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
> | debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
> | debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
> | debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
> | debug1: Host 'ultra.fxq.nl' is known and matches the DSA host key.
> | debug1: Found key in /home/ed/.ssh/known_hosts:12
> | debug1: ssh_dss_verify: signature correct
> | debug1: SSH2_MSG_NEWKEYS sent
> | debug1: expecting SSH2_MSG_NEWKEYS
> | debug1: SSH2_MSG_NEWKEYS received
> | debug1: SSH2_MSG_SERVICE_REQUEST sent
> | debug1: SSH2_MSG_SERVICE_ACCEPT received
> | debug1: Authentications that can continue: publickey,keyboard-interactive
> | debug1: Next authentication method: publickey
> | debug1: Offering public key: /home/ed/.ssh/id_rsa
> | debug1: Server accepts key: pkalg ssh-rsa blen 149
> | debug1: Authentication succeeded (publickey).
> | debug1: channel 0: new [client-session]
> | debug1: Entering interactive session.
> | Received disconnect from 2001:7b8:310::1: 2: dup #1 failed: Bad file descriptor
> 
> Thank goodness I discovered that running `ssh ultra sh' does work, so I
> enabled a telnetd with just some very simple shell commands (no TTY
> means no vi).
> 
> When I connect to the machine using SSH, the following messages pop up
> in the log messages:
> 
> | Jul  5 14:23:46 ultra sshd[1021]: error: ioctl(TIOCSCTTY): Bad file descriptor
> | Jul  5 14:23:46 ultra sshd[1021]: error: open /dev/tty failed - could not set controlling tty: Device not configured
> | Jul  5 14:23:46 ultra sshd[1021]: error: dup2 stdin: Bad file descriptor
> | Jul  5 14:23:46 ultra sshd[1021]: error: dup2 stdout: Bad file descriptor
> | Jul  5 14:23:46 ultra sshd[1021]: error: dup2 stderr: Bad file descriptor
> 
> Is there anyone else who is seeing this behaviour as well?

And then, does telnet works ? In particular, do you get tty when telnetting
into the box, does command like "echo aaa >/dev/tty" work from telnet session ?


Received on Thu Jul 05 2007 - 10:51:56 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:13 UTC