Warnings from openssh-4.3p1 configure

[Tim Rice]

On Thu, 9 Feb 2006, Tim Rice wrote:

> On Thu, 9 Feb 2006, Mark Zimmerman wrote:
> 
> > On Thu, Feb 09, 2006 at 02:00:21PM -0800, Tim Rice wrote:
> > > On Thu, 9 Feb 2006, Mark Zimmerman wrote:
> > > 
> > > > Greetings:
> > > > 
> > > > Well, I tried the latest snapshot and it configures without warnings
> > > > and it compiles, but it doesn't work...
> > > 
> > > Very suprising.
> > > Do a diff in the 2 config.h files and send it to me.
> > > What platform is this?
> > 
> > foghorn$ uname -a
> > SunOS cswfsu01 5.8 Generic_117350-31 sun4u sparc SUNW,Sun-Fire-V440
> > 
> > 
> > foghorn$ diff openssh-4.3p1/config.h openssh/config.h
> [diff sniped]
> Looks right.
> 
> > > > foghorn$ ./ssh gaim
> > > > Disconnecting: Bad packet length 1423594411.
> > > > foghorn$ ./ssh -V
> > > > OpenSSH_4.3p1-snap20060208, OpenSSL 0.9.8a 11 Oct 2005
> 
> Try the 20060210 snap. That's what's in CVS.
> 
> It's working fine here.
> SunOS sun2 5.8 Generic_117350-31 sun4u sparc SUNW,Ultra-2
> But then I'm using openssl 0.9.7
> 
> [hours pass, more building/testing]
> I just built a current 0.9.8 and tested again. regression tests fail.
> Hmm.
> 
> Tests OK with 0.9.8 on my UnixWare box.
> 
> I'll do more testing as time permits.

I may have an idea.

I'm guessing that there is a problem with running 2 versions of
the openssl shared libs. My Solaris box is seg faulting.
....
27822:  getpid()                                        = 27822 [27821]
27822:      Incurred fault #6, FLTBOUNDS  %pc = 0xFF2328D0
27822:        siginfo: SIGSEGV SEGV_MAPERR addr=0x00000014
27822:      Received signal #11, SIGSEGV [default]
27822:        siginfo: SIGSEGV SEGV_MAPERR addr=0x00000014
27822:          *** process killed ***
27828:  read(7, 0xFFBEE410, 4)                          = 0
27828:  write(2, " d e b u g 1 :   d o _ c".., 20)      = 20
27828:  _exit(255)
....

But my UnixWare 7.1.1 box does not.

The Soaris box has a bunch of other shared libs that use the openssl 0.9.7
shared libs. This openssh test run was built with 0.9.8 shared libs.

I'm suspecting that this can't work.

Anyone have any thoughts on this?

Mark, do a truss on the sshd that fails and see what openssl libs it
opens.

-- 
Tim Rice				Multitalents	(707) 887-1469
tim at multitalents.net