Re: PINE: SIG 6

		
On May 19, 2007, at 2:59 PM, Alexander Kabaev wrote:

> Now, you need to know contents of s, s->session, session->sess_cert  
> and
> s->session->sess_cert->peer_dh_tmp from frame #7.
>
> I have no time do to the debugging over email and I am not really
> interested until someone else traces this to GCC problem.
>
> The email from Pieter de Goeje seems to indicate that libssl code
> seems to be at fault.
>
> -- 
> Alexander Kabaev

1) I can give access to the machine/core
2) I'm not an expert.

Here is what you asked for:
gdb) fr 7
#7  0x0000000800d4374d in ssl3_send_client_key_exchange (s=0x80154e180)
     at /usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/ 
s3_clnt.c:1845
1845                            if (s->session->sess_cert- 
 >peer_dh_tmp != NULL)
(gdb) print s->session->sess_cert->peer_dh_tmp
$1 = (DH *) 0x8014341e0
(gdb) print *$1
$2 = {pad = 0, version = 0, p = 0x80152b800, g = 0x80152b860, length  
= 0,
   pub_key = 0x80152bdc0, priv_key = 0x0, flags = 1, method_mont_p =  
0x0, q = 0x0,
   j = 0x0, seed = 0x0, seedlen = 0, counter = 0x0, references = 1,  
ex_data = {
     sk = 0x0, dummy = -1515870811}, meth = 0x8010d63e0, engine = 0x0}
(gdb)


I can give shell/sudo access to any developer that wants to look into  
this.

If libssl is at fault, who/what do I need to do?

LER


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 512-248-2683                 E-Mail: ler_at_lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893