Suhosin Installation Failure

Discussion in 'Installation/Configuration' started by ChaosTheory, Jan 31, 2011.

  1. ChaosTheory

    ChaosTheory New Member

    I am trying ton install Suhosin following the how to guide http://www.howtoforge.com/php_suhosin_centos5.0_p2

    I am installing on a VPS via SSH, and everything goes fine until this step:
    Code:
    rpmbuild -ba php.spec
    After installing the required dependancies I am currently getting the following output:


    Code:
    Patch #117 (php-5.1.6-CVE-2010-3870.patch):
    + patch -p1 -b --suffix .cve3870 -s
    + echo 'Patch #210 (php-5.2.1-suhosin.patch):'
    Patch #210 (php-5.2.1-suhosin.patch):
    + patch -p1 -b --suffix .suhosin -s
    1 out of 1 hunk FAILED -- saving rejects to file ext/standard/basic_functions.c.rej
    1 out of 1 hunk FAILED -- saving rejects to file ext/standard/file.h.rej
    2 out of 8 hunks FAILED -- saving rejects to file main/main.c.rej
    1 out of 1 hunk FAILED -- saving rejects to file sapi/cgi/cgi_main.c.rej
    1 out of 1 hunk FAILED -- saving rejects to file sapi/cli/php_cli.c.rej
    1 out of 2 hunks FAILED -- saving rejects to file win32/build/config.w32.rej
    15 out of 16 hunks FAILED -- saving rejects to file Zend/zend_alloc.c.rej
    1 out of 1 hunk FAILED -- saving rejects to file Zend/zend_alloc.h.rej
    error: Bad exit status from /var/tmp/rpm-tmp.7221 (%prep)
    
    I found a similar post a year or two back that was having a similar problem and they suggested moving the suhosin patch to the end of the list in the php.spec file, and while that allowed me to get further, no matter where I put it in the list once it hits the suhosin patch it returns that failure. I check the output folder (RPMS/x86_64) and it is empty as well.

    Any suggestons?
     
  2. falko

    falko Super Moderator ISPConfig Developer

    You msut use the Suhosin patch for PHP 5.1.6 (that's the PHP version that comes with CentOS 5.x), not 5.2.1.
     
  3. ChaosTheory

    ChaosTheory New Member

    My php was upgraded to 5.2.17, thus I used the 5.2.1 patch. For now I have just upgraded to 5.3.5 since there are supposed to be some critical security fixes in that. I have installed the Suhosin extension (which installed flawlessly) and will wait for the coressponding patch to come out and will try that one then.

    Thanks!
     

Share This Page