Date: Sat, 19 May 2007 15:04:41 -0500 From: Larry Rosenman <ler@lerctr.org> To: Alexander Kabaev <kabaev@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: PINE: SIG 6 Message-ID: <B86D4453-6748-4AA2-BCB6-ED3D622DFFE0@lerctr.org> In-Reply-To: <8F80AFD4-C83E-413F-8158-CFD27453AE87@lerctr.org> References: <299DD8FD-0E7A-4E3D-9902-2C7FE45AA7BC@lerctr.org> <20070519141503.07e94a36@kan.dnsalias.net> <E3B706CD-FBD7-45A3-B3D3-1AB8BE2DA2A3@lerctr.org> <20070519143105.65072348@kan.dnsalias.net> <9F2A10A0-2B58-4BE4-8DD0-9D7811B6BCE6@lerctr.org> <20070519155919.453081a5@kan.dnsalias.net> <8F80AFD4-C83E-413F-8158-CFD27453AE87@lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 19, 2007, at 3:02 PM, Larry Rosenman wrote:
>
> 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
>
Here are the other prints:
(gdb) print s->session
$3 = (SSL_SESSION *) 0x80143aa00
(gdb) print *$3
$4 = {ssl_version = 769, key_arg_length = 0, key_arg = "\000\000\000
\000\000\000\000",
master_key_length = 0, master_key = '\0' <repeats 47 times>,
session_id_length = 32,
session_id = "D\032?Q&4a\212_q??????N#\177?<?$?H\fu?[?\237\"",
sid_ctx_length = 0,
sid_ctx = '\0' <repeats 31 times>, not_resumable = 0, sess_cert =
0x80152c1c0,
peer = 0x801437560, verify_result = 19, references = 1, timeout =
7200,
time = 1179603504, compress_meth = 0, cipher = 0x0, cipher_id = 0,
ciphers = 0x0,
ex_data = {sk = 0x0, dummy = 0}, prev = 0x0, next = 0x0}
(gdb) print s->session->sess_cert
$5 = (struct sess_cert_st *) 0x80152c1c0
(gdb) print *$5
$6 = {cert_chain = 0x80152aac0, peer_cert_type = 0, peer_key =
0x80152c1d8,
peer_pkeys = {{x509 = 0x801437560, privatekey = 0x0}, {x509 = 0x0,
privatekey = 0x0}, {x509 = 0x0, privatekey = 0x0}, {x509 = 0x0,
privatekey = 0x0}, {x509 = 0x0, privatekey = 0x0}, {x509 = 0x0,
privatekey = 0x0}}, peer_rsa_tmp = 0x0, peer_dh_tmp =
0x8014341e0,
peer_ecdh_tmp = 0x0, references = 1}
(gdb)
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
> US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
>
>
>
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B86D4453-6748-4AA2-BCB6-ED3D622DFFE0>