similar to: ssh client hangs on exit!

Hi, I use openssh-2.9p2 on LynxOS i386 system. sshd runs on LynxOS and ssh client on Redhat 7.0 Linux system (openssh-2.9p2 ssh client). The ssh client hangs on exit 90% of times. I don't think this is the usual hang-on-exit bug, because, there are no background processes running, I suppose. I attach the server debug messages. $ssh -V hari at lynx (From Linux) ... Password: ... lynx>

Hi, I use openssh-2.9p2 on a LynxOS i386 system. The ssh and scp clients work fine. Even sftp from other Linux systems works. But, if I make sftp to the localhost (LynxOS), the authentication succeeds, prints sftp> prompt and then exits. I don't know why this happens. I have not set the euid of ssh program to root as it does not work in LynxOS (may be problem with saved ids). Might this

Hi, I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am connecting from a ssh client (openssh-2.9p2) on an x86 Linux box. This works fine for ssh protocol version 1, but am getting the below error for ssh v2: Disconnecting: Bad packet length -857542839. I am also attaching the complete debug traces from sshd & ssh below. I am not sure if this is an "endian" issue.

Hi, I have ported the portable version of openssh (openssh-2.9p2) to LynxOS. I have had to install Perl5 and openssl-0.9.5a. Also since the regex library in LynxOS is not POSIX compliant I had to use PCRE. Then I configured openssh-2.9p2 with the library option -lbsd. One more problem was the macro "howmany(x,y)" is not defined in any of the /usr/include header files n LynxOS. So I

Hi, using OpenSSH_2.1.1 p4 i have problems with X11 forwarding. I used the same sources for Solaris and Linux. Tried nearly every combination, but it seems that the "opensshd" for Solaris has some problems. Of course i tried to connect with "ssh -X", the server has in its /etc/sshd_config: X11Forwarding yes X11DisplayOffset 10 XAuthLocation /usr/openwin/bin/xauth The client

Hi, With reference to my previous mail: 1. I use openssh-2.9p2 on a LynxOS i386 system. The ssh and scp clients work fine. Even sftp from other Linux systems works. But, if I run the sftp client in LynxOS to localhost (LynxOS) or remote sshd in Linux, the authentication succeeds, prints sftp> prompt and then exits. I don't know why this happens. The problem is with the sftp client

Hi, I work on openssh-2.9p2 installed on LynxOS i386 system. sshd, ssh, scp and sftp-server all work fine. The problem is sftp client, in interactive mode, exits after authentication printing the sftp prompt. sftp client works fine in non-interactive mode. i.e., lynxos>sftp hari at linuxsystem:test works fine But, lynxos>sftp hari at linuxsystem ... sftp> lynxos> Any help, as to why

Hi, 1. Does ssh, scp and sftp client programs work on LynxOS? I use openssh-2.9p2 on a LynxOS i386 system. The ssh and scp clients work fine. Even sftp from other Linux systems works. But, if I make sftp to the localhost (LynxOS), the authentication succeeds, prints sftp> prompt and then exits. I don't know why this happens. I have not set the euid of ssh program to root as it does not

I'm not a ssh expert and I don't know if the log is good or bad, but I too am running OpenSHH under OpenServer. I find that after I connect, the return key has no effect unless I first type: stty sane <Ctrl>j If you've hit <ENTER> before that you must first press <Ctrl>j a couple of times to clean out the buffer. After I type the above command, everything

To whomsoever it may concern, I use putty-0.51 as ssh client on windows and openssh-2.9p2 implementation on RedHat 7.0 Linux as ssh server. For the client to exit, I expected ssh client to send SSH_CMSG_EOF to the server and the server respond with SSH_CMSG_EXITSTATUS and finally close the connection when the client sends SSH_CMSG_EXIT_CONFIRMATION. This will effectively end the server_loop in

Greetings: I've just attempted to upgrade from openssh-2.1.1p1 to openssh-2.1.1p3 and I'm having problems with the server component. My system runs RedHat Linux 6.2 (x86 version) with all currently released updates applied. The sshd daemon is being spawned by xinetd with the -i option and worked fine with the p1 level release. Now, when a remote client attempts to connect to the daemon,

When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4 to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little while (of inactivity?) I get the following message on the client terminal: Disconnecting: protocol error: rcvd type 98 Looking further, this message is actually caused by the SSH daemon. However, I'm at a loss to determine why sshd is doing this. I attach

To whoever can help me, I tried to compile OpenSSH-2.9p2 on i386-LynxOS. I made a # ./configure --without-pam --without-shadow \ --with-ssl-dir=/usr/local/ssl --with-pcre \ --disable-libutil --sysconfdir=/etc/ssh Then, # make gave the following error: gcc -o ssh ssh.o sshconnect.o sshconnect1.o sshconnect2.o sshtty.o reonf.o clientloop.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -lssh

Hi, I just grabed the 2.9p2 and can't forward X11 connections. This worked fine for me under 2.9p1 but with 2.9p2 it seems that $XAUTHORITY isn't getting set and when I try and set it manually connections to the Xserver still fail with: debug1: X11 connection uses different authentication protocol. debug1: X11 rejected 1 i1/o16 Verbose debugs below. client: OpenSSH_2.9p1, SSH

Hello, I tried to install Samba-2.0.8 and Samba 2.2.0 on our LynxOS System. uname -a: LynxOS imklynxa 3.0.1 110298-G i386 gcc --version: 2.7-97r1 First problem in both packets: There is no LynxOS Version 3.0.1 in config.guess. I added 3 lines and tried again. configure ended only with a WARNING about the Network interface. Second Problem I had with the make command. Second Problem at 2.0.8:

Hi, This patch includes port of NUT to LynxOS 4.0. The patch is against yesterday's svn tree. Here is a brief description of changes: drivers/powercom.c: Rename shutdown() to shutdown2(). shutdown() is already defined in LynxOS system header files. Please feel free to rename it more appropriately. (I didn't do it due to lack of imagination :-) ) include/proto.h: Added

[Steve Snyder <swsnyder@home.com>] > When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was > told that configure could determine my operating system. > > LynxOS, for those that don't know, is a Unix-like RTOS. It comes > with a binary version of Samba, but a) it's old and b) it's not built > for encrypted passwords which means I can't

Whoever can help me... pls find attached the loggings for the openssh sessions from local(host=keg;redhat linux) to remote (host=ben;lynxos) The issue is when I run sshd in debug mode and try to logon from local, password authentication succeeds, but if I run sshd as a daemon, it fails. sshlocal.txt >>> logging at local when sshd is not run with debug option sshlocal...txt >>

When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was told that configure could determine my operating system. LynxOS, for those that don't know, is a Unix-like RTOS. It comes with a binary version of Samba, but a) it's old and b) it's not built for encrypted passwords which means I can't access it from WinNT. Can anyone advise me on what it would take to build

Olli Savia wrote: > The attached patch is a port of the current CVS (2005-08-11) version > of OpenSSH portable to LynxOS. Could you consider adding it to the > future releases of OpenSSH? If the patch needs additional work, please > let me know. Looks mostly reasonable, some comments and questions below. > + AC_DEFINE(LYNXOS_BROKEN_SETVBUF, 1, [LynxOS has broken setvbuf()