[sslh] sslh-1.7a - problem with zombies

Bud Curry Bud at computereaseofmd.com
Tue Jul 13 22:45:20 CEST 2010


Sorry, I guess that was harsh.

Possibly this is the root of my evil:

2010-07-13 02:09:15 192.168.1.1 2290 192.168.1.2 443 HTTP/1.1 POST
/Microsoft-Server-ActiveSync?User=******&DeviceId=**********************
**&DeviceType=PocketPC&Cmd=Ping - 1 Connection_Abandoned_By_AppPool
ExchangeApplicationPool 

-----Original Message-----
From: Yves Rutschle [mailto:yves at naryves.com] 
Sent: Tuesday, July 13, 2010 4:41 PM
To: Bud Curry
Cc: Rich Rauenzahn; Matthias Buecher / Germany; sslh at rutschle.net
Subject: Re: [sslh] sslh-1.7a - problem with zombies

On Tue, Jul 13, 2010 at 12:54:33PM -0400, Bud Curry wrote:
> That said, I'm not sure why we're not believing sslh is the source of 
> the zombies.  In my mind, there's no doubt.

We're not saying sslh is not the source. However we do know it works
properly in a number of configurations. The goal here is to isolate what
makes sslh misbehave in your configuration to fix it.

My plan from here is to build uClibc and compile sslh against it on my
setup to see if I can reproduce the bug. If I can, then I'll see about
fixing it. If the bug still doesn't appear, we'll be back to square one
and trying to figure out what's different in your setup compared to all
the others that work (and again -- not saying your setup is faulty here,
the great things about standards is that is there are so many to choose
from, and no-one really implements them exactly, so sslh may be simply
tripping over something in the standards that's open for interpretation,
and that behaves one way in uClibc and another in GNU libc).

I won't have time to built that kind of stuff until the end of the month
though. (in particular tomorrow is dedicated to barbeques and fireworks
country-wide so I won't be replying to e-mail -- fear not, I'll be back
to work on thursday).

Y.







More information about the sslh mailing list