Hello,

 I have been experiencing segfaults with Apache while using the
"builtin" random generator with the two following configurations :

*  Linux 2.2.12 SMP (RedHat 6.2), Apache 1.3.12 (stock RedHat), 
   mod_php 3.0.16 (homebuilt), mod_ssl 2.6.2 (stock RPM from 
   www.modssl.org/contrib), openssl 0.9.5 (i586 version from 
   http://www.megaloman.com/~hany/RPM/openssl.html).

*  Same as the above (same machine) except mod_ssl 2.6.4 and openssl
   0.9.5a (as specified in README.Versions) ; still stock RPMs from
   the same places.

  Each time I checked, the segfault appeared in the function 
SHA1_Update(). Here is a stack trace (note that the address
0x404aeb37 points in the middle of an instruction...)
#0  0x404aeb37 in SHA1_Update () from /usr/lib/libcrypto.so.0
#1  0x404e249e in ssleay_rand_add () from /usr/lib/libcrypto.so.0
#2  0x404e25f2 in ssleay_rand_seed () from /usr/lib/libcrypto.so.0
#3  0x404e2f0e in RAND_seed () from /usr/lib/libcrypto.so.0
#4  0x40282d1e in ssl_rand_seed () from /usr/lib/apache/libssl.so
#5  0x40280bb8 in ssl_hook_NewConnection () from /usr/lib/apache/libssl.so
#6  0x805ab53 in ap_start_restart ()
#7  0x805b913 in ap_child_terminate ()
#8  0x805bb2f in ap_child_terminate ()
#9  0x805bddc in ap_child_terminate ()
#10 0x805c1b7 in ap_child_terminate ()
#11 0x805c65f in main ()

  The stack trace remains the same even when LD_PRELOAD-ing Electric
Fence, which clearly designates this function as the culprit. I had
other segfaults from Apache processes that died without having served
any SSL pages (according to my logs - I can't tell whether they 
died in their first attempt to do so) ; but these segfaults went 
away when I changed the random source to /dev/urandom in the
server config files.

  Best regards,

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

Reply via email to