From owner-freebsd-emulation Mon Mar 19 8:39:28 2001 Delivered-To: freebsd-emulation@freebsd.org Received: from k2.jozsef.kando.hu (k2.jozsef.kando.hu [193.224.40.3]) by hub.freebsd.org (Postfix) with SMTP id CD70837B71C for ; Mon, 19 Mar 2001 08:39:22 -0800 (PST) (envelope-from bra@fsn.hu) Received: (qmail 19220 invoked by uid 1000); 19 Mar 2001 16:39:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 19 Mar 2001 16:39:20 -0000 Date: Mon, 19 Mar 2001 17:39:20 +0100 (CET) From: Attila Nagy X-X-Sender: To: Subject: logging in with linux openssh binary Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have to set up a complete linux (debian) system on a FreeBSD 4.3-BETA system. I've tarred out the base2_2.tgz (ftp.debian.org/debian/dists/potato/main/disks-i386/current) and configured the nameserver in /etc/resolv.conf and added the first user. Everything works like a charm until now, but I have a serious problem with OpenSSH. I do the following: # chroot /compat/linux /bin/bash # sshd -d debug: sshd version OpenSSH-1.2.3 debug: Bind to port 22 on 1.2.3.4. Server listening on 1.2.3.4 port 22. Generating 768 bit RSA key. RSA key generation complete. [now I try to connect with an ssh client from another machine using the username added previously] debug: Server will not fork when running in debugging mode. Connection from 1.1.1.1 port 1521 debug: Client protocol version 1.5; client software version OpenSSH-1.2.3 debug: Sent 768 bit public key and 1024 bit host key. debug: Encryption type: 3des debug: Received session key; encryption turned on. debug: Installing crc compensation attack detector. debug: checking for shadow entry debug: completed shadow checks debug: Starting up PAM with username "bra" debug: Attempting authentication for bra. Failed rsa for bra from 1.1.1.1 port 1521 [This is normal, now I type in the password at the other end] debug: PAM setting rhost to "resolved IP" debug: Allocating pty. error: openpty: Inappropriate ioctl for device error: Failed to allocate pty. debug: Forking shell. debug: PAM establishing creds debug: Entering interactive session. I've tried several things. First the OpenSSH process has hung at "Allocating pty", because on newer Linux systems the preferred method is to use /dev/pts/xx instead of the old ptys. After the deletion of the /dev/ptmx which is needed for this kind of operation I got the above. I've tried to recreate the device nodes with FreeBSD's MAKEDEV without success. I got the same error. After ktrace'ing the above I see: 13939 sshd CALL open(0x28233e36,0x2,0x2807d4d8) 13939 sshd NAMI "/compat/linux/dev/ptmx" 13939 sshd NAMI "/dev/ptmx" 13939 sshd RET open JUSTRETURN 13939 sshd CALL open(0xbfbfe078,0x2,0) 13939 sshd NAMI "/compat/linux/dev/ptyp0" 13939 sshd NAMI "/dev/ptyp0" 13939 sshd RET open -1 errno -5 Unknown error: -5 13939 sshd CALL open(0xbfbfe078,0x2,0xbfbfe084) 13939 sshd NAMI "/compat/linux/dev/ptyp1" 13939 sshd NAMI "/dev/ptyp1" 13939 sshd RET open 3 13939 sshd CALL ioctl(0x3,0x5401 ,0xbfbfcef0) 13939 sshd RET ioctl -1 errno -11 Unknown error: -11 13939 sshd CALL close(0x3) 13939 sshd RET close 0 13939 sshd CALL write(0x2,0xbfbfc294,0x2f) 13939 sshd GIO fd 2 wrote 47 bytes "error: openpty: Inappropriate ioctl for device [...] (this is the case with the FreeBSD pty device nodes) And the sshd keeps on going, the client gets some output, but can't type in anything. Besides recommending to use vmware, plex86, or something similar emulators (I can't and don't want because they are slow and unstable) or to use FreeBSD's native ssh to log in (in this situation this is not what I want) could you please give me some clues about this? Thanks, -------------------------------------------------------------------------- Attila Nagy e-mail: Attila.Nagy@fsn.hu Budapest Polytechnic (BMF.HU) @work: +361 210 1415 (194) H-1084 Budapest, Tavaszmezo u. 15-17. cell.: +3630 306 6758 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message