ID: 7322 Comment by: bduell at ncacasi dot org Reported By: andrew at neuimage dot com Status: Closed Bug Type: Reproducible Crash Operating System: Linux-2.2.17 PHP Version: 4.0.3 New Comment:
I have verified, through VeriSign, that the SDK of PayflowPro (currently, v. 3.06) is statically linked against the openssl libraries. They have no plans on changing this design, therefor we will be changing payment processors. Good luck! Previous Comments: ------------------------------------------------------------------------ [2001-01-07 08:41:26] [EMAIL PROTECTED] This is a known problem with the pfpro module provided by Verisign (FWIW, closed proprietary source), and not php. ------------------------------------------------------------------------ [2001-01-07 04:00:56] [EMAIL PROTECTED] Does this happen with PHP 4.0.4 ? Or with openssl 0.9.6 ? --Jani ------------------------------------------------------------------------ [2000-10-18 17:23:31] andrew at neuimage dot com Hello - I have spoken with Verisign regarding setting up PayFlow Pro on my Linux server, via PHP on an Apache server, with mod_ssl. The problem that I encounter, is that once I have php compiled, apache compiled w/ php + ssl modules enabled, I can't get apache to run. It gives me a segmentation fault every time I run it, and I'm not sure what to do. Whenever I take out either the SSL, or PFPro Module from PHP, the daemon works perfectly. I looked through some documentation on the pfpro library, and I think I might have a reason why it won't work. It appears that Verisign uses SSLeay for their SSL encryption, while my Apache server uses mod_ssl. I don't know if the two can work together, and this might be what we're up against. I tried compiling apache+ssl, which uses the SSLeay library, and the deamon ran, but it segfaulted any time I tried to pull something on the webserver. It's crucial that I am able to have SSL and PFPro modules working on the same server, because this server will handle all of our transactions (billing, accounting, controls, etc), and it must be secure, whilst have access to Verisign. Here is my php configure command: ./configure --with-mysql=/sql --with-apache=../apache_1.3.12 --enable-track-vars --enable-sockets --with-pfpro=/usr/local/signio/linux/lib --enable-ftp --with-imap=/usr/lib Here is my apache configure command: ./configure --with-layout=Apache --enable-module=speling --enable-module=info --enable-module=ssl --activate-m odule=src/modules/php4/libphp4.a --enable-module=php4 --server-gid=www --prefix=/apache Here is the gdb output: ------ ([EMAIL PROTECTED]:/apache) gdb bin/httpd core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)... Core was generated by `bin/httpd -X'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Reading symbols from /usr/local/signio/linux/lib/libpfpro.so...(no debugging symbols found)...done. Reading symbols from /sql/lib/mysql/libmysqlclient.so.6...(no debugging symbols found)...done. Reading symbols from /usr/lib/libpng.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done. Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done. Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done. Reading symbols from /lib/libcrypt.so.1...done. Reading symbols from /lib/libnsl.so.1...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libpthread.so.0...done. Reading symbols from /lib/libnss_compat.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. Reading symbols from /lib/libnss_db.so.2...done. Reading symbols from /lib/libdb.so.3...done. #0 0x40075c44 in ProcessPNTransaction () from /usr/local/signio/linux/lib/libpfpro.so (gdb) ------ If you could provide me with either a configuration which will work, or some other means of getting past this roadblock, It would be much appreciated. Thank You ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=7322&edit=1
