Upgraded to 2.9p1 with no luck..

[Ladner, Eric (CLAD)]

Hmm.. Oddly enough, if I run this as root, connecting to the same user on
the other machine with "ssh -l clad pgppt", it works.  Also used this, 
"ssh -2 -l clad -i /home/clad/.ssh/id_rsa pgppt" to force V2 and
authenticate
aginst my own key.  It still works.  Kinda throws a wrinkle into me running
this under root and debugging it.

I'm going to scratch my head on this a bit..

Thanks,

Eric 

-----Original Message-----
From: Lutz Jaenicke [mailto:Lutz.Jaenicke at aet.TU-Cottbus.DE]
Sent: Friday, May 25, 2001 2:27 PM
To: 'openssh-unix-dev at mindrot.org'
Subject: Re: Upgraded to 2.9p1 with no luck..


On Fri, May 25, 2001 at 12:04:57PM -0700, Ladner, Eric (CLAD) wrote:
> After upgrading to 2.9 (OpenSSH_2.9p1, SSH protocols 1.5/2.0, OpenSSL
> 0x0090600f) 
> I'm unable to ssh between two systems any more (the two that I've
upgraded).

> Below are some relevant snippets of debugging output around where the
error
> occurs.  
> Feel free to contact me regarding any additional information required.  
> 
> Output from "ssh -v -v -v pgppt" executed on a HP C240 workstation (HP-UX
> 11.0, 
> PA-RISC 1.1):

I am running 2.9p1 on HP-UX 10.20 (platforms are from 710 to C200), so there
is certain probability that we can get it to run :-)

> debug1: channel 0: new [client-session]
> debug1: channel_new: 0
> debug1: send channel open 0
> Memory fault
This is the point to step into debugging. From a Memory fault you should
either get a core dump (but ssh is suid root, so you probably won't get
one) or you can run it under a debugger and will end up at the location
causing the memory fault. You must perform this as root, since ssh is
suid root.

Best regards,
	Lutz
-- 
Lutz Jaenicke                             Lutz.Jaenicke at aet.TU-Cottbus.DE
BTU Cottbus               http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik                  Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cottbus              Fax. +49 355 69-4153