pfpro issues

Hi folks- I've been running into some trouble with the extension that David Croft and I wrote for real-time credit card processing. Basically, Verisign (formerly Signio) provides a binary .so that we've written wrapper functions around. This is what we link against when you enable the extension. Unfortunately, this .so file statically links some version of OpenSSL, with an unknown compiler/linker. So, if you compile Curl support into a CGI version of PHP, or if you compile PHP as an apache module when apache+modssl is linked against OpenSSL, it causes all kinds of runtime problems (segfaults). The ideal solution, obviously, is getting Verisign to open up the source, or at least some parts of it, and let us statically link their library into PHP. I know Verisign well enough to assume this isn't in the cards, but I will ask them. I have a feeling our luck would be better with Signio had Signio not been purchased by Verisign, but, oh well. Right now, the extension is only useful if you compile the CGI version of PHP without linking OpenSSL into it (which works fine for batch processing) or if you compile it into Apache without modssl, which is very unlikely with any sort of ecommerce application. For all other cases, the scripts will still have to vfork and call the command-line client you can compile out of Verisign's SDK. Anyways, being a PHP hacker turned C dabbler, I don't presume to know that I've exhausted all options in trying to fix these problems. Has anyone else run into a similar situation? I remember seeing a similar issue with apache + mod_auth_mysql + php+--with-mysql, but that is probably different in the sense that you can link every component with the same linker, where as I have no control over Verisign's .so. Is there any way to relink a binary-only .so file against our own version of OpenSSL? Muchas gracias -- John Donagher Application Engineer Intacct Corp. - Powerful Accounting on the Web 408-395-0989 720 University Ave. Los Gatos CA 95032 www.intacct.com -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDnCZ1oRBACFgkFCV6p3dWic1qm1FLhip5beIyzZSt+ccTDYQQdPZA/t5H+k PZ7ZFBIUrXz/oEqwQwlEKlg8JQqg7hgtcL+xrIJ0BInLeSJG4lvvB551g59Thr7/ OsdxNVxKci775+K+GkdAz4xcULMuB+QE7t665Ri46EAS8ALos5UG6DGmhwCguD0v 1cxwy/KlKr+oi4sWM9caueED/RmjiSD3vmBZQt6PMisVe1AmkEf6cJoemduCSJxu 0eMz/LIeu+CqfpuJH2N/dZ3hRj9xMSHF4l71wKqV99zhm58kDGwG1u3yVzULPDqz 0yL+8nunlkoOUyn3zOnh3Zmz4POFVMZQ5oian3QkLllUwly5JCi5tWULxZ2vOkb0 zzjuA/4jigNxYV4NAyCl+wAbnyzk9/Iz8EHv4/0Ex8ytlcMtvBJKa9HjJxlyIl74 yOILHk3+GSAdM0b3ZmbavpoCpebinOMBhqEVBwCI4VUIAqf86gx+2dKBGxfKPnU4 Xxvqs/BOl/EbeJjyd4uieYndGRaWg+kYXqZ7SxrlFN24fohnd7QgSm9obiBEb25h Z2hlciA8am9obkB3ZWJtZXRhLmNvbT6IVgQTEQIAFgUCOcJnWgQLCgQDAxUDAgMW AgECF4AACgkQIt6tVu6+jd3SHwCgjssFktMXf8NjE9JBR+sJ2gDIsW8An0CFNdFd dU+DJYC6ogYP9AsVfM27uQENBDnCZ2MQBAD8E0qe1gBKjtoRmyiyORtwhOz/2XZE mqiZN2NouAUWRRZd4dHggFAA1jUsp2MVIZZQyY9ajNVy3Oaxj5kYz8LR5GItxxcD jC8RFXKM40ZfTJeR7fH6eJa689w+le71Tt4ALyN4xcjSWuksr8795AhHFjonDi8D rgGIq6GtWvi/KwADBgQAmeBbcjPzhqR2M8TdvEyNfVTQSSp/RNoTjNNWpHui8V0p kiQ49tbsqeMjXGToGgMugfmrX77JidXyuVjgYjT9xUdaaA25qKAR75M9izDliT7Y h5L+QZTAw0/5X9go7XK3WI3LYfFrp4TP0veXgSWxDqccqsRzWKW7IoXsliTCbVqI RgQYEQIABgUCOcJnYwAKCRAi3q1W7r6N3YIcAKCkJMTPLu6tOPnXPl2s3xmnSawy BACeOx83WlBhVScYWo+BUzntJ6ks4T0= =OkJU -----END PGP PUBLIC KEY BLOCK-----