FAQ
From: eric at vlender dot com
Operating system: GNU/Linux (slackware)
PHP version: 4.3.1
PHP Bug Type: OpenSSL related
Bug description: SSL and cURL SSL break with pfpro

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.

Search Discussions

  • Sniper at Feb 26, 2003 at 4:36 pm
    ID: 22441
    Updated by: sniper@php.net
    Reported By: eric at vlender dot com
    -Status: Open
    +Status: Feedback
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    New Comment:

    You most likely have too old version of the pfpro SDK.
    (old ones have some ssl funcs in it which clash with openssl)



    Previous Comments:
    ------------------------------------------------------------------------

    [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=22441&edit=1
  • Eric at vlender dot com at Feb 26, 2003 at 5:12 pm
    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:

    I don't think that is the case. I am using the following shared
    library from the sdk:
    -rwxrwxr-x 1 501 501 690560 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.


    Previous Comments:
    ------------------------------------------------------------------------

    [2003-02-26 10:36:31] sniper@php.net

    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=22441&edit=1
  • Eric at vlender dot com at Feb 26, 2003 at 5:19 pm
    ID: 22441
    User updated by: eric at vlender dot com
    Reported By: eric at vlender dot com
    Status: Open
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    New Comment:

    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.


    Previous Comments:
    ------------------------------------------------------------------------

    [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-x 1 501 501 690560 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] sniper@php.net

    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=22441&edit=1
  • Sniper at Feb 26, 2003 at 5:25 pm
    ID: 22441
    Updated by: sniper@php.net
    Reported By: eric at vlender dot com
    -Status: Open
    +Status: Feedback
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    New Comment:

    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..)



    Previous Comments:
    ------------------------------------------------------------------------

    [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-x 1 501 501 690560 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] sniper@php.net

    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=22441&edit=1
  • Eric at vlender dot com at Feb 26, 2003 at 5:37 pm
    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] sniper@php.net

    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-x 1 501 501 690560 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] sniper@php.net

    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=22441&edit=1
  • Eric at vlender dot com at Mar 1, 2003 at 1:19 am
    ID: 22441
    User updated by: eric at vlender dot com
    Reported By: eric at vlender dot com
    Status: Open
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    New Comment:

    Well, I have now compiled in openssl-0.9.7a and cURL-7.10.3 and instead
    of just getting nothing, I get this in my logs:
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11916 exit signal
    Segmentation fault (11)
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11908 exit signal
    Segmentation fault (11)

    That is with an attempted fsockopen("ssl://securehost.hre", 443,
    errorno, error); call that works perfectly with out the -pfpro option
    ...

    I guess I can always have PHP shell out to a PERL script and manage the
    transaction ..

    Thanks for your help :)


    Previous Comments:
    ------------------------------------------------------------------------

    [2003-02-26 11:37:47] eric at vlender dot com

    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

    ------------------------------------------------------------------------

    [2003-02-26 11:25:56] sniper@php.net

    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-x 1 501 501 690560 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] sniper@php.net

    You most likely have too old version of the pfpro SDK.
    (old ones have some ssl funcs in it which clash with openssl)


    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://bugs.php.net/22441

    --
    Edit this bug report at http://bugs.php.net/?id=22441&edit=1
  • Sniper at Mar 5, 2003 at 2:11 am
    ID: 22441
    Updated by: sniper@php.net
    Reported By: eric at vlender dot com
    -Status: Open
    +Status: Feedback
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    New Comment:

    Does compiling PHP as DSO for Apache fix this?
    If so, you can bogus this, we already have a report about that one.




    Previous Comments:
    ------------------------------------------------------------------------

    [2003-02-28 19:19:56] eric at vlender dot com

    Well, I have now compiled in openssl-0.9.7a and cURL-7.10.3 and instead
    of just getting nothing, I get this in my logs:
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11916 exit signal
    Segmentation fault (11)
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11908 exit signal
    Segmentation fault (11)

    That is with an attempted fsockopen("ssl://securehost.hre", 443,
    errorno, error); call that works perfectly with out the -pfpro option
    ...

    I guess I can always have PHP shell out to a PERL script and manage the
    transaction ..

    Thanks for your help :)

    ------------------------------------------------------------------------

    [2003-02-26 11:37:47] eric at vlender dot com

    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

    ------------------------------------------------------------------------

    [2003-02-26 11:25:56] sniper@php.net

    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-x 1 501 501 690560 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.

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://bugs.php.net/22441

    --
    Edit this bug report at http://bugs.php.net/?id=22441&edit=1
  • Sniper at Mar 10, 2003 at 1:15 am
    ID: 22441
    Updated by: sniper@php.net
    Reported By: eric at vlender dot com
    -Status: Feedback
    +Status: No Feedback
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    New Comment:

    No feedback was provided. The bug is being suspended because
    we assume that you are no longer experiencing the problem.
    If this is not the case and you are able to provide the
    information that was requested earlier, please do so and
    change the status of the bug back to "Open". Thank you.




    Previous Comments:
    ------------------------------------------------------------------------

    [2003-03-04 20:11:07] sniper@php.net

    Does compiling PHP as DSO for Apache fix this?
    If so, you can bogus this, we already have a report about that one.



    ------------------------------------------------------------------------

    [2003-02-28 19:19:56] eric at vlender dot com

    Well, I have now compiled in openssl-0.9.7a and cURL-7.10.3 and instead
    of just getting nothing, I get this in my logs:
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11916 exit signal
    Segmentation fault (11)
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11908 exit signal
    Segmentation fault (11)

    That is with an attempted fsockopen("ssl://securehost.hre", 443,
    errorno, error); call that works perfectly with out the -pfpro option
    ...

    I guess I can always have PHP shell out to a PERL script and manage the
    transaction ..

    Thanks for your help :)

    ------------------------------------------------------------------------

    [2003-02-26 11:37:47] eric at vlender dot com

    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

    ------------------------------------------------------------------------

    [2003-02-26 11:25:56] sniper@php.net

    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.

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://bugs.php.net/22441

    --
    Edit this bug report at http://bugs.php.net/?id=22441&edit=1
  • Bduell at ncacasi dot org at Aug 5, 2003 at 3:38 pm
    ID: 22441
    Comment by: bduell at ncacasi dot org
    Reported By: eric at vlender dot com
    Status: No Feedback
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    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:
    ------------------------------------------------------------------------

    [2003-03-09 19:15:13] sniper@php.net

    No feedback was provided. The bug is being suspended because
    we assume that you are no longer experiencing the problem.
    If this is not the case and you are able to provide the
    information that was requested earlier, please do so and
    change the status of the bug back to "Open". Thank you.



    ------------------------------------------------------------------------

    [2003-03-04 20:11:07] sniper@php.net

    Does compiling PHP as DSO for Apache fix this?
    If so, you can bogus this, we already have a report about that one.



    ------------------------------------------------------------------------

    [2003-02-28 19:19:56] eric at vlender dot com

    Well, I have now compiled in openssl-0.9.7a and cURL-7.10.3 and instead
    of just getting nothing, I get this in my logs:
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11916 exit signal
    Segmentation fault (11)
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11908 exit signal
    Segmentation fault (11)

    That is with an attempted fsockopen("ssl://securehost.hre", 443,
    errorno, error); call that works perfectly with out the -pfpro option
    ...

    I guess I can always have PHP shell out to a PERL script and manage the
    transaction ..

    Thanks for your help :)

    ------------------------------------------------------------------------

    [2003-02-26 11:37:47] eric at vlender dot com

    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

    ------------------------------------------------------------------------

    [2003-02-26 11:25:56] sniper@php.net

    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..)


    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://bugs.php.net/22441

    --
    Edit this bug report at http://bugs.php.net/?id=22441&edit=1
  • Jvinet at zeroflux dot org at Oct 29, 2007 at 9:01 pm
    ID: 22441
    Comment by: jvinet at zeroflux dot org
    Reported By: eric at vlender dot com
    Status: No Feedback
    Bug Type: OpenSSL related
    Operating System: GNU/Linux (slackware)
    PHP Version: 4.3.1
    New Comment:

    I've had the same problem with the old/deprecated pfpro sdk and PHP
    4.4.7.

    When the extension is built into the php binary (--with-pfpro=DIR),
    cURL breaks with https:// URLs.

    When the extension is built as a shared module
    (--with-pfpro=shared,DIR), cURL works.

    Hope this helps, though in the long run, I'd recommend moving away from
    any reliance on the pfpro SDK.


    Previous Comments:
    ------------------------------------------------------------------------

    [2003-08-05 10:38:31] bduell at ncacasi dot org

    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!

    ------------------------------------------------------------------------

    [2003-03-09 19:15:13] sniper@php.net

    No feedback was provided. The bug is being suspended because
    we assume that you are no longer experiencing the problem.
    If this is not the case and you are able to provide the
    information that was requested earlier, please do so and
    change the status of the bug back to "Open". Thank you.



    ------------------------------------------------------------------------

    [2003-03-04 20:11:07] sniper@php.net

    Does compiling PHP as DSO for Apache fix this?
    If so, you can bogus this, we already have a report about that one.



    ------------------------------------------------------------------------

    [2003-02-28 19:19:56] eric at vlender dot com

    Well, I have now compiled in openssl-0.9.7a and cURL-7.10.3 and instead
    of just getting nothing, I get this in my logs:
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11916 exit signal
    Segmentation fault (11)
    [Fri Feb 28 18:19:46 2003] [notice] child pid 11908 exit signal
    Segmentation fault (11)

    That is with an attempted fsockopen("ssl://securehost.hre", 443,
    errorno, error); call that works perfectly with out the -pfpro option
    ...

    I guess I can always have PHP shell out to a PERL script and manage the
    transaction ..

    Thanks for your help :)

    ------------------------------------------------------------------------

    [2003-02-26 11:37:47] eric at vlender dot com

    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

    ------------------------------------------------------------------------

    The remainder of the comments for this report are too long. To view
    the rest of the comments, please view the bug report online at
    http://bugs.php.net/22441

    --
    Edit this bug report at http://bugs.php.net/?id=22441&edit=1

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupphp-bugs @
categoriesphp
postedFeb 26, '03 at 4:30p
activeOct 29, '07 at 9:01p
posts11
users2
websitephp.net

People

Translate

site design / logo © 2022 Grokbase