I'm running OpenLDAP linked with OpenSSL 0.9.8e on the sparcv9 (64-bit) 
architecture. This received a SIGBUS, so something is misaligned somewhere 
along the line. To a quick reading of the code, the area in question was 
allocated in SSL_new and is being modified by ssl3_accept with minimal 
processing by OpenLDAP, so I'm running with the theory (along with the 
OpenLDAP developers) that this is an issue in OpenSSL. Below, please find 
the stack trace from the OpenLDAP crash.


[EMAIL PROTECTED] ([EMAIL PROTECTED]) terminated by signal BUS (invalid address 
alignment)
0xffffffff7d24fab8: t_delete+0x00f8:    stx      %o0, [%g4 + 16]
current thread: [EMAIL PROTECTED]
   [1] t_delete(0x11c303480, 0x0, 0xffffffff7f268340, 0x2000, 0x2190, 
0x1004e4290), at 0xffffffff7d24fab8
   [2] _malloc_unlocked(0x80, 0x0, 0x0, 0x11ad552e0, 0x11ad552e0, 0x0), at 
0xffffffff7d24f068
   [3] malloc(0x80, 0xffffffff7e502458, 0xffffffff7e5014f0, 0xf68, 0x24fd00, 
0xc00), at 0xffffffff7d24ee94
=>[4] CRYPTO_malloc(num = ???, file = ???, line = ???) (optimized), at 
0xffffffff7e2b2274 (line ~304) in "mem.c"
   [5] bn_expand_internal(b = ???, words = ???) (optimized), at 
0xffffffff7e308140 (line ~336) in "bn_lib.c"
   [6] BN_bin2bn(s = ???, len = ???, ret = ???) (optimized), at 
0xffffffff7e308940 (line ~451) in "bn_lib.c"
   [7] RSA_eay_private_decrypt(flen = ???, from = ???, to = ???, rsa = ???, 
padding = ???) (optimized), at 0xffffffff7e32f160 (line ~517) in "rsa_eay.c"
   [8] ssl3_get_client_key_exchange(s = ???) (optimized), at 0xffffffff7e625150 
(line ~1732) in "s3_srvr.c"
   [9] ssl3_accept(s = ???) (optimized), at 0xffffffff7e6227d0 (line ~449) in 
"s3_srvr.c"
   [10] ldap_pvt_tls_accept(sb = 0x11be3ac90, ctx_arg = 0x1004e4290), line 866 
in "tls.c"
   [11] connection_read(s = 189), line 1348 in "connection.c"
   [12] slapd_daemon_task(ptr = (nil)), line 2359 in "daemon.c"

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to