Client Log

OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.1.253 [192.168.1.253] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type 1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6
debug1: match: OpenSSH_4.6 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
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 '192.168.1.253' is known and matches the DSA host key.
debug1: Found key in /root/.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,password
debug1: Next authentication method: publickey
debug1: Trying private key: /root/.ssh/identity
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /root/.ssh/id_dsa
debug1: Next authentication method: password
hostmeister@192.168.1.253's password:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8

Server Error Log:


sshd: error: openpty: No such file or directory
sshd: error: session_pty_req: session 0 alloc failed

Solution (Enable Legacy PTY because it's a new option in Kernel 3)

Edit .config

Virtual terminal (VT) [Y/?] y
  Support for binding and unbinding console drivers (VT_HW_CONSOLE_BINDING) [Y/n/?] y
Unix98 PTY support (UNIX98_PTYS) [Y/?] y
  Support multiple instances of devpts (DEVPTS_MULTIPLE_INSTANCES) [Y/n/?] y
Legacy (BSD) PTY support (LEGACY_PTYS) [Y/n/?] y
  Maximum number of legacy PTY in use (LEGACY_PTY_COUNT) [256] (NEW) y


ssh, login, hangclient, openssh_, openssl, fips, rhel, jul, debug, configuration, etc, ssh_config, applying, connecting, established, permanently_set_uid, id_rsa, id_dsa, protocol, software, openssh, enabling, compatibility, mode, _msg_kexinit, kex, server, aes, cbc, hmac, md, _msg_kex_dh_gex_request, _msg_kex_dh_gex_group, _msg_kex_dh_gex_init, _msg_kex_dh_gex_reply, dsa, known_hosts, ssh_dss_verify, _msg_newkeys, _msg_service_request, _msg_service_accept, authentications, publickey, password, authentication, method, hostmeister, succeeded, interactive, env, lang, en_us, utf, sshd, openpty, directory, session_pty_req, alloc, enable, legacy, pty, kernel, edit, config, virtual, terminal, vt, binding, unbinding, console, drivers, vt_hw_console_binding, unix, _ptys, multiple, instances, devpts, devpts_multiple_instances, bsd, legacy_ptys, maximum, legacy_pty_count,

Latest Articles