Jonathan Houser wrote:
Aarno,
IMHO, going that far back is counterproductive. But if Kannel leaks on error,
failed fetchs should generate leaks, do they not ? And then we will have a
reproducable bug.
I was just comparing the oldest version I tested that still leaked against mine that doesn't. I did the diff of those two to minimize the size of the diff file.
I tried to break it with a simulator asking for URLs like "http://catchow";, "http://catchow.ruffy.com/"; and "http://10.10.0.3"; with no luck. I then tried to log in to Hotmail...
http://mobile.msn.com/ select 'MSN Hotmail'
...with my simulator (Ericsson WapIDE 3.2.1), which uses OpenSSL, and that worked. It failed like the previous OpenSSL lines I've pasted and inc'ed the CLOSE_WAIT count. Below are the lines that *could* apply to it. (As an aside, is there any way to log an IP address with each line? It'd *really* help in debugging. Then I could pull lines that apply to my IP vs. some carrier's IP in cases like this.)
2005-03-02 10:43:10 [16976] [7] INFO: Fetching URL <http://mobile.msn.com/wml/prelogin.aspx?ru=%2fhm%2ffolder.aspx> for MSISDN <>
2005-03-02 10:43:10 [26681] [8] WARNING: WSP: Content type <text/html> not supported by client, deleting body.
2005-03-02 10:43:10 [24336] [1] ERROR: WSP: Do not know how to encode header type 65
2005-03-02 10:43:10 [24336] [1] WARNING: Skipping header: Set-Cookie: cr=1; path=/
2005-03-02 10:43:10 [24336] [1] WARNING: WSP headers: cannot decode date '-1'
2005-03-02 10:43:10 [16976] [7] INFO: Fetching URL <http://mobile.msn.com/wml/prelogin.aspx?ru=%2fhm%2ffolder.aspx&ct=774187213> for MSISDN <>
2005-03-02 10:43:10 [24336] [1] ERROR: WSP: Do not know how to encode header type 65
2005-03-02 10:43:10 [24336] [1] WARNING: Skipping header: Set-Cookie: cr=1; path=/
2005-03-02 10:43:10 [24336] [1] WARNING: WSP headers: cannot decode date '-1'
2005-03-02 10:43:10 [16976] [7] INFO: Fetching URL <http://login.passport.com/login.srf?lc=1033&id=961&ru=http%3a%2f%2fmobile.msn.com%2fwml%2fmigrate.aspx%3freturl%3d%252fhm%252ffolder.aspx&mlc=en-US&mspsty=mobile&tw=14400&kv=5&ct=1109778274&ns=hotmail.com&ver=2.5.1016.0> for MSISDN <>
2005-03-02 10:43:10 [26681] [8] WARNING: WSP: Device doesn't support charset <iso-8859-1> neither UTF-8
2005-03-02 10:43:10 [24336] [1] ERROR: WSP: Do not know how to encode header type 65
2005-03-02 10:43:10 [24336] [1] WARNING: Skipping header: Set-Cookie: MSPRequ=lt=1109778274&co=1&id=961
2005-03-02 10:43:10 [16976] [7] INFO: Fetching URL <https://mobile.passport.net/si/default.aspx?lc=1033&id=961&ru=http%3a%2f%2fmobile.msn.com%2fwml%2fmigrate.aspx%3freturl%3d%252fhm%252ffolder.aspx&mlc=en-US&mspsty=mobile&tw=14400&kv=5&ct=1109778274&ns=hotmail.com&ver=2.5.1016.0&rollrs=11> for MSISDN <>
2005-03-02 10:43:10 [26379] [16] ERROR: SSL write failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL write failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL read failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL read failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL write failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL write failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL write failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL read failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL read failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: SSL write failed: OpenSSL error 1: error:00000001:lib(0):func(0):reason(1)
2005-03-02 10:43:10 [26379] [16] ERROR: Couldn't fetch <https://mobile.passport.net/si/default.aspx?lc=1033&id=961&ru=http%3a%2f%2fmobile.msn.com%2fwml%2fmigrate.aspx%3freturl%3d%252fhm%252ffolder.aspx&mlc=en-US&mspsty=mobile&tw=14400&kv=5&ct=1109778274&ns=hotmail.com&ver=2.5.1016.0&rollrs=11>
2005-03-02 10:43:10 [26681] [8] ERROR: WSP: HTTP lookup failed, oops.
2005-03-02 10:43:10 [26681] [8] WARNING: WSP: Content type <text/plain> not supported by client, deleting body.
ok, I just traced for some hours now issues from the openssl ssl lib code within Kannel's gwlib/conn.[ch] regarding failures while SSLv[23] protocol handshake etc., no obvious bug to me.
Generally the error code 1 for the SSL_read/write here means from openssl docs: generic SSL libary failure.
A post in a mailing-list of curl gave an hint that peer verification is always "on" per default for client mode SSL contexts. This is also set via SSL_CTX_set_verify() within gwlib/conn.c:conn_config_ssl() accordingly and is called within wapbox.c.
So, currently I don't see a reason for the openssl error here.
Anyone having in-deep expertise with openssl to have it's hands put on this issue?
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
