Recent changes to support-requests

chroot() in 5.0_r1

Doug Eckert — Thu, 29 Jan 2009 21:40:57 -0000

Trying to jail user(s) into their home directories. Seem to have everything set up properly, and can manually chroot from command line. In sshd_config I've got

Match user dj999999
ChrootDirectory /home/chroot

But when the user (dj999999) attempts an ssh login, 'sshd -dd' shows the following before the conenction is torn down:

debug2: User child is on pid 196688
debug1: PAM: establishing credentials
debug1: TMP*****************:/home/chroot
debug1: CHROOT_PATH*********:/home/chroot
debug1: pw->pw_name:dj999999::pw->pw_dir:/home/chroot/./home/dj999999/
chroot("/home/chroot"): Operation not permitted.
debug1: do_cleanup
debug1: do_cleanup
debug1: PAM: cleanup
debug1: PAM: deleting credentials
debug1: PAM: closing session
debug1: audit event euid 0 user dj999999 event 12 (SSH_connabndn)
debug1: Return Val-1 for auditproc:0

Is chroot not implemented (yet)? If not, when?

PAM support

Patrick Beaudoin — Mon, 08 Sep 2008 14:32:11 -0000

Is that possible to have PAM support enabled when build the package?

Thanks!!

LDAP support

Karim Ben — Mon, 30 Jun 2008 15:15:58 -0000

Hello,

Could you provide package OpenSSH with patch LPK (Ldap Public Key).

I need to store ssh key on a container in the directory ldap.

Thanks in advance for your help.

Session closed from 'root' even success authenticated

Anonymous — Wed, 28 May 2008 13:55:10 -0000

I have installed openssh 4.7 and openssl 0.9.8f as suggested by IBM on both AIX5.2ML8 and AIX5.3TL5.

Installation for both OS release has no issue.

However, for for AIX 5.2, when I directly open a session using 'root' account, the session closes even after successful authenticated, using password or public key.

Pls see below debug output.

OpenSSH_4.7p1, OpenSSL 0.9.8f 11 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Failed dlopen: /usr/krb5/lib/libkrb5.a(libkrb5.a.so): 0509-022 Cannot load module /usr/krb5/lib/libkrb5.a(libkrb5.a.so).
0509-026 System error: A file or directory in the path name does not exist.

debug1: Error loading Kerberos, disabling Kerberos auth.
debug2: ssh_connect: needpriv 0
debug1: Connecting to tla2 [10.30.14.102] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /.ssh/identity type -1
debug3: Not a RSA1 key file /.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /.ssh/id_rsa type 1
debug3: Not a RSA1 key file /.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7
debug1: match: OpenSSH_4.7 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7
debug2: fd 4 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_setup: found hmac-md5
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
debug2: dh_gen_key: priv key bits set: 141/256
debug2: bits set: 503/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /.ssh/known_hosts
debug3: check_host_in_hostfile: match line 116
debug3: check_host_in_hostfile: filename /.ssh/known_hosts
debug3: check_host_in_hostfile: match line 116
debug1: Host 'tla2' is known and matches the RSA host key.
debug1: Found key in /.ssh/known_hosts:116
debug2: bits set: 525/1024
debug1: ssh_rsa_verify: signature correct
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /.ssh/identity (0)
debug2: key: /.ssh/id_rsa (20044d38)
debug2: key: /.ssh/id_dsa (20044d58)
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug3: start over, passed a different list publickey,password,keyboard-interactive
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /.ssh/identity
debug3: no such identity: /.ssh/identity
debug1: Offering public key: /.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Offering public key: /.ssh/id_dsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-dss blen 434
debug2: input_userauth_pk_ok: fp 65:bb:84:06:53:eb:57:6a:85:e2:a3:b8:d4:38:b2:a7
debug3: sign_and_send_pubkey
debug1: read PEM private key done: type DSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t3 r-1 i0/0 o0/0 fd 5/6 cfd -1)

debug3: channel 0: close_fds r 5 w 6 e 7 c -1
Connection to tla2 closed by remote host.
Connection to tla2 closed.
debug1: Transferred: stdin 0, stdout 0, stderr 71 bytes in 0.0 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 11957.3
debug1: Exit status -1

Security vulnerability - X11 forwarding

Ken Robinson — Thu, 03 Apr 2008 23:18:54 -0000

A CVE for OpenSSH was released last week forcing the OpenSSH community to release version 5.0 to address this vulnerability. There are many organizations taking this vulnerability seriously. What is the plan for releasing the new version to fix this vulnerability?

Installation problem around openssl

ewertman — Mon, 17 Dec 2007 16:20:38 -0000

I'm trying to install the instllp 4.5 openssh package, but I'm getting a failure on the installed version of openssl.

I have openssl v0.9.7 installed:

rpm -qa | grep -i open
openssl-0.9.7l-2

# oslevel -r
5300-06

But the installp fails:

FAILURES
--------
Filesets listed in this section failed pre-installation verification
and will not be installed.

Requisite Failures
------------------
SELECTED FILESETS: The following is a list of filesets that you asked to
install. They cannot be installed until all of their requisite filesets
are also installed. See subsequent lists for details of requisites.

openssh.base.server 4.5.0.5301 # Open Secure Shell Server

MISSING REQUISITES: The following filesets are required by one or more
of the selected filesets listed above. They are not currently installed
and could not be found on the installation media.

openssl.base 0.9.8.4 # Fileset Update

<< End of Failure Section >>

SUCCESSES
---------
Filesets listed in this section passed pre-installation verification
and will be installed.

Selected Filesets
-----------------
openssh.base.client 4.5.0.5301 # Open Secure Shell Commands
openssh.license 4.5.0.5301 # Open Secure Shell License
openssh.man.en_US 4.5.0.5301 # Open Secure Shell Documentat...
openssh.msg.en_US 4.5.0.5301 # Open Secure Shell Messages -...

<< End of Success Section >>

FILESET STATISTICS
------------------
5 Selected to be installed, of which:
4 Passed pre-installation verification
1 FAILED pre-installation verification
----
4 Total to be installed

I think I don't want to change the ssl version installed, because it will break some other dependencies (python, for one).

Need more than 100 LocalForward entries

Richard Ross — Thu, 27 Sep 2007 18:22:47 -0000

Received "too many local forwards (max 100)". We have a large number of systems in an isolated network and need to have more than 100 LocalForward entries. Please recompile to allow 500 LocalForward entries.

Archive Naming

jgann — Thu, 21 Jun 2007 14:14:36 -0000

Hello,

Thanks for fixing the -A (agent forwarding) issue on 5.2.

Anyway, I would appreciate very much if the openssh release archives were named according to some scheme.

For now it is most confusing and releases cannot be told apart:

current is openssh-4.3p2_r2_52.tar.Z
last was openssh-4.3p2-52-r2.tar.Z

I see that the "4.3p2" part comes with the source but something like, say, adding 1 to the r-Part with every new Release would be extremely helpful. Likewise, adding 1 to the Fileset Level would allow the user to identify, which release he has got installed:

Fileset Level State Type Description (Uninstaller)
----------------------------------------------------------------------------
openssh.base.client 4.3.0.5201 C F Open Secure Shell Commands
openssh.base.server 4.3.0.5201 C F Open Secure Shell Server
openssh.license 4.3.0.5201 C F Open Secure Shell License
openssh.man.en_US 4.3.0.5201 C F Open Secure Shell
Documentation - U.S. English
openssh.msg.en_US 4.3.0.5201 C F Open Secure Shell Messages -
U.S. English

Thanks and Best Regards,
jgann

OpenSSH 4.6p1

Anonymous — Mon, 21 May 2007 18:54:40 -0000

Hello, I work for IBM as an FTSS for System p. My customer, AT&T, is looking for the latest compiled version of OPENSSH (v4.6p1 or v4.6) for AIX v5.1, 5.2, & 5.3. Can you please let me know when this will be provided? It appears that you are several versions downlevel and there is quite a bit more functionality provided in the current version of OpenSSH. Please respond to this e-mail: acfowler@us.ibm.com

ssh login freezes; sshd setsid error

Dan Bryan — Mon, 11 Sep 2006 16:20:24 -0000

I have installed openssh-4.3p2_53.tar.Z on AIX 5.3 (no
ML). When connecting using SSH, I enter the
username/password, then the connection freezes.

The last messages on the ssh debug are:

debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: channel 0: request pty-req
debug1: channel 0: request shell
debug1: channel 0: open confirm rwindow 0 rmax 32768

The last on sshd debug are:

debug3: tty_parse_modes: 91 1
debug3: tty_parse_modes: 92 0
debug3: tty_parse_modes: 93 0
debug1: server_input_channel_req: channel 0 request
shell reply 0
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req shell
debug2: fd 3 setting TCP_NODELAY
debug2: channel 0: rfd 8 isatty
debug2: fd 8 setting O_NONBLOCK
debug3: fd 7 is O_NONBLOCK
setsid: Operation not permitted.

I'd be grateful for any advice.

Thank you
Dan.