openssh-2.3.0p1 on HP-UX 11.00 went mad

[Ulrich Windl]

Hi,

I had a strange effect: I tried to debug a program with GNU debugger 
when very strange messages appeared on the screen. Like:

(gdb) Undefined command: "3".  Try "help".
(gdb) Undefined command: "".  Try "help".
(gdb) Undefined command: "".  Try "help".
(gdb) Undefined command: "".  Try "help".

I found out that a co-worked security-tested the machine with SAINT. 
Thus the syslog said this about SSH:

rkdvmhp3 sshd[4041]: Bad protocol version identification 'QUIT
rkdvmhp3 sshd[4095]: Did not receive ident string from 132.199.206.2.

The truely odd thing is that gdb seems to work normally when
I try to capture the output via "script", so it might be a terminal
thing. Anyway I succeeded to capture the output:

/opt/gdb/bin/gdb ~windl/src/C++/HCM/HCMextract 
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "hppa2.0n-hp-hpux11.00"...
(gdb) (gdb) (gdb) 466	#if 1
467	////
468	// Workaround: "return(x)" does not set exit code
469	////
470	#define return(x)	exit(x)
471	#endif
472	
473	/* main program parses arguments and begins execution */
474	int	main(int argc, char *argv[])
475	{
(gdb) Undefined command: "".  Try "help".
(gdb) Undefined command: "".  Try "help".
(gdb) The history is empty.
(gdb) Undefined command: "".  Try "help".
(gdb) Undefined command: "".  Try "help".
(gdb) Undefined command: "".  Try "help".
(gdb) Undefined command: "".  Try "help".
(gdb) Undefined command: "4".  Try "help".
(gdb) (gdb) Undefined command: "".  Try "help".
(gdb) 476		SCOPE("main");
477		int	status_fd;
478		int	option;
479		int	bad_syntax = 0;
480		char	path[PATH_MAX + 1];
481		char		*next_elem;
---Type <return> to continue, or q <return> to quit--- j---Type 
<return> to continue, or q <return> to quit--- j
(arg: 1)  
j8) 
---Type <return> to continue, or q <return> to 
quit---  jj        
j | x 
t p h 
L @ < 
8 8 48  < @ L h p t x |    j 

j--Type <return> to continue, or q <return> to quit---4 48  < @ L h p t 
x |    j

 j-Type <return> to continue, or q <return> to quit--- $48  < @ L h p t x 
|    

j--Type <return> to continue, or q <return> to quit--- $, $48 
 < @ L h p t x |   

 --Type <return> to continue, or q <return> to quit---, , $48  < 
@ L h p t x |  

  -Type <return> to continue, or q <return> to quit--- 4, $48  < @ 
L h p t x | 

   Type <return> to continue, or q <return> to quit--- 
4---Type <return> to continue, or q <return> to quit--- 4, $48  < 
@ L h p t x | 

   j je <return> to continue, or q <return> to quit---  4, $48  < @ L h p 
t x |

    ype <return> to continue, or q <return> to quit--- 4, $48  < @ 
L h p t x | 

   Type <return> to continue, or q <return> to quit---

482	

To make things worse, the gdb runs normally if I log in directly as "v11adm". 
In the previous attempt I logged in as "root" and did a "su - v11adm". Rather 
puzzled. Can anybody make any sense in this?

Regards,
Ulrich