Very Computer

When connecting to the site with a 40-bit browser, things seem to run
smoothly.  However, when running a 128-bit browser and connecting to the
same site (I've tested this with both IE and Netscape), I get a network
error (unable to connect to host) and it logs a segmentation fault in the
error_log.

Has anyone seen this behaviour before?  I've run this same setup numerous
times on FreeBSD, but this is my first time doing it on Linux, and it's not
proving to be a fun ordeal ;)

Thanks,

J.

is  http://core.freshmeat.net/appindex/1998/08/23/903863187.html what you need
??

Here's an excerpt from the error_log:

httpd: [Fri Mar  5 15:46:43 1999] [notice] child pid 15880 exit signal
Segmentation fault (11)
httpd: [Fri Mar  5 15:46:46 1999] [notice] child pid 15869 exit signal
Segmentation fault (11)
httpd: [Fri Mar  5 15:46:52 1999] [error] mod_ssl: SSL handshake failed
(client 206.108.237.36, server proxy.elecomm.net:443) (OpenSSL library error
follows)
httpd: [Fri Mar  5 15:46:52 1999] [error] OpenSSL: error:0407106B:rsa
routines:RSA_padding_check_PKCS1_type_2:block type is not 02
httpd: [Fri Mar  5 15:46:52 1999] [error] OpenSSL: error:04065072:rsa
routines:RSA_EAY_PRIVATE_DECRYPT:padding check failed
httpd: [Fri Mar  5 15:46:52 1999] [error] OpenSSL: error:1408F071:SSL
routines:SSL3_GET_RECORD:bad mac decode
httpd: [Fri Mar  5 15:46:55 1999] [error] mod_ssl: SSL handshake failed
(client 206.108.237.36, server proxy.elecomm.net:443) (OpenSSL library error
follows)
httpd: [Fri Mar  5 15:46:55 1999] [error] OpenSSL: error:0407106B:rsa
routines:RSA_padding_check_PKCS1_type_2:block type is not 02
httpd: [Fri Mar  5 15:46:55 1999] [error] OpenSSL: error:04065072:rsa
routines:RSA_EAY_PRIVATE_DECRYPT:padding check failed
httpd: [Fri Mar  5 15:46:55 1999] [error] OpenSSL: error:1408F071:SSL
routines:SSL3_GET_RECORD:bad mac decode

How do I do the backtrace?  It's not dumping core.

J.