Hit this from a different angle, via request tracker using oracle-client
and Net::LDAP.
In my opinion the bug's really with the oracle client. I was able to work
around this by setting
LD_PRELOAD=/usr/lib/libcrypto.so.0.9.8
before launching the application. That doesn't seem to have hurt. I should
add, I've no idea if the oracle-client is actually attempting to use its
internal SSL library or not in its connection. It's quite possible that if
it does, then this workaround will cause a segfault somewhere under
DBD::Oracle rather than IO::Socket::SSL.
--
jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/
Tel +44 (0)117 3317661 http://ioctl.org/jan/
Goth isn't dead, it's just lying very still and sucking its cheeks in.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
