Actually, let me amend my problem description a bit: Interactive sessions have the same problem as command-line-supplied commands when run under hostbased authentication. When I exit from the shell, menu, or "uptime" command, the client will not exit until I hit Enter and the server sees an EOF. Sorry if that caused confusion. -- Gregor Mosheh [EMAIL PROTECTED] Systems Admin, Humboldt Internet 707.825.4638 ---------- Forwarded message ---------- Date: Wed, 29 Mar 2000 13:22:41 -0800 (PST) From: Gregor Mosheh <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: hostname authentication hangs on Solaris 2.6 I grabbed the SSH 2.0.1 Beta 1 and I'm having the same problem as always. To be specific: I set up hostbased authentication by copying a client machine's public key into /etc/ssh2/knownhosts/CLIENTNAME.ssh-dss.pub and adding "hostbased" to the list of AllowedAuthentications. Interactive sessions work great. The problem is running a command on the client's command-line. The client can connect and run a command with a line like "ssh -l someuser SERVERNAME uptime", but the SSH doesn't exit after the command is run. The session will sit until I press Enter, when I get a Connection Closed message. Running the server with -v looks all great. It finds the key and forks my command: debug: Ssh2Common/sshcommon.c:521/ssh_common_new_channel: num_channels now 1 debug: Ssh2ChannelSession/sshchsession.c:927/ssh_channel_session_exec: Forking without pty On the client, I get the output from the "uptime" command. But the client doesn't exit and return me to a shell. It just sits. Eventually, when I press Enter on the client side, the server says this as the client and server exit: debug: SshConnection/sshconn.c:610/ssh_conn_channel_write: EOF received on write from channel 0x115a70, extended stream 0. FATAL: ssh_pipe_get_exit_status called before the child has exited. -- Gregor Mosheh [EMAIL PROTECTED] Systems Admin, Humboldt Internet 707.825.4638 On Wed, 29 Mar 2000, Sami Lehtinen wrote: > Gregor Mosheh writes: > : > : I went over this exact same problem with one of the developers for a month > : or so and we never were able to figure out the problem. Maybe it'll be > : fixed accidentally in the next version... > > Have you tried the ssh-2.1.0.public.beta.1 ? It is very likely fixed > in that. > > Try it. You can find it in http://www.ssh.com . > > -- > [[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]] > [work:+358 9 43543218][gsm:+358 50 5170 258][http://www.iki.fi/~sjl] > [SSH Communications Security Ltd. http://www.ssh.fi/] >
