ID: 22441
User updated by: eric at vlender dot com
Reported By: eric at vlender dot com
-Status: Feedback
+Status: Open
Bug Type: OpenSSL related
Operating System: GNU/Linux (slackware)
PHP Version: 4.3.1
New Comment:
On a quick side note, Payflow pro is working perfectly. We use it for
our signups, and the signup procedure is functioning perfectly. Just
cURL and fsockopen() are not happy.. :(
I placed them in /usr/lib and /usr/local/include respectfully.
/usr/local/lib/pfpro.h is a symlink to the header in
/usr/local/include
~ locate pfpro | sort
/usr/lib/libpfpro.so
/usr/local/include/pfpro.h
/usr/local/lib/pfpro.h
/usr/local/src/php-4.3.1/ext/pfpro
/usr/local/src/php-4.3.1/ext/pfpro/CREDITS
/usr/local/src/php-4.3.1/ext/pfpro/TODO
/usr/local/src/php-4.3.1/ext/pfpro/config.m4
/usr/local/src/php-4.3.1/ext/pfpro/pfpro.c
/usr/local/src/php-4.3.1/ext/pfpro/pfpro.lo
/usr/local/src/php-4.3.1/ext/pfpro/pfpro.o
/usr/local/src/php-4.3.1/ext/pfpro/php_pfpro.h
/usr/local/src/php-4.3.1/tests/testpfpro.php
Previous Comments:
[2003-02-26 11:25:56] [EMAIL PROTECTED]
Where are the pfpro libs and headers installed then?
And you're absolutely sure you don't have any older versions
laying around? (I somewhat remember there being some problems before
with pfpro and openssl..)
[2003-02-26 11:19:14] eric at vlender dot com
One other note that I realized should probally be taken into account
with this. I am using apache-ssl Ben-SSL/1.48 and not mod_ssl.
[2003-02-26 11:12:34] eric at vlender dot com
I don't think that is the case. I am using the following shared
library from the sdk:
-rwxrwxr-x1 501 501690560 Jun 11 2002 libpfpro.so*
I went and redownloaded the SDK this morning, and the lib in their
download is the same as this one. Here are my configure statements.
(Also, in the meantime I have upgraded to openssl-0.9.7)
apache-1.3.27: ./configure --prefix=/usr/local/apache
--server-uid=daemon --server-gid=daemon
--activate-module=src/modules/php4/libphp4.a:
php-4.3.1: ./configure --with-apache=../apache_1.3.27 --enable-bcmath
--with-curl --with-gettext --with-mysql=/usr/local/mysql
--with-mcrypt=../libmcrypt-2.5.0 --with-openssl=/usr/local/ssl
--with-pear --disable-cgi --with-gd --with-zlib
--with-jpeg-dir=/usr/lib --with-pfpro
With just the --with-pfpro option I believe it uses the PHP internal
pfpro extension, is this the issue, and should I be pointing it to the
pfpro shared library instead?
If so, will I need to recompile everything as shared? I prefer static
for the raw performance, but will switch to shared if that will solve
this issue.
Thanks again.
[2003-02-26 10:36:31] [EMAIL PROTECTED]
You most likely have too old version of the pfpro SDK.
(old ones have some ssl funcs in it which clash with openssl)
[2003-02-26 10:30:04] eric at vlender dot com
php-4.3.1 / apache 1.3.27 / openssl-0.9.6g / curl-7.10.2
When ever I use the --with-pfpro configure option to compile in payflow
pro support, it breaks the cURL (--with-curl) SSL connectability, as
well as fsockopen(ssl://somehost.hst)(--with-openssl=/usr/local/ssl)
functionality.
If I recompile with out the payflow-pro extension I can use
curl_init(); and fsockopen(ssl:) again. It took me quite awhile to
figure this one out, since curl_init() and fsockopen(ssl:) don't return
any errors when --pfpro is compiled in. They just do not work at all.
No errors, no initalization, nothing.
Thanks for your time.
--
Edit this bug report at http://bugs.php.net/?id=22441edit=1
