| Summary: | Hardenedphp USE flag does not appear to include the hardenedphp patch on emerge | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | lou <whitehatcheck> |
| Component: | Current packages | Assignee: | PHP Bugs <php-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | christian.hartmann, marek.wiecek |
| Priority: | Highest | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Patch to php-sapi.eclass to handle newer php and hardened-php versions
Updated patch to php-sapi.eclass to handle php-4.3.11 Working patch for php-4.3.11 |
||
|
Description
lou
2004-12-18 13:51:23 UTC
Created attachment 46700 [details, diff]
Patch to php-sapi.eclass to handle newer php and hardened-php versions
This patch adds the correct hardened-php versions to the php-sapi.eclass for
all versions of PHP4 currently on the portage tree, now that hardened-php is
finally available for the more recent versions of PHP.
Added the patch to eclass.. now receiving digest error. Not sure if I need to create digest (emerge hardened-php-4.3.10-0.2.6.patch.gz digest) within /usr/portage/dev-php/mod_php. Can you advise? !!! No message digest entry found for file "hardened-php-4.3.10-0.2.6.patch.gz." !!! Most likely a temporary problem. Try 'emerge sync' again later. !!! If you are certain of the authenticity of the file then you may type !!! the following to generate a new digest: !!! ebuild /usr/portage/category/package/package-version.ebuild digest Lou, You might want to try running ebuild /usr/portage/dev-php/mod_php/mod_php-4.3.10.ebuild digest as the error suggests *** Bug 89155 has been marked as a duplicate of this bug. *** Why is this trivial bug still unfixed? That's a very good question. Comments? Created attachment 57415 [details, diff]
Updated patch to php-sapi.eclass to handle php-4.3.11
This is an updated version of the previous patch, adding support for
php-4.3.11. Unfortunately, there seems to be a bug in portage preventing the
eclass from correctly adding the address of the patch to SRC_URI.
Created attachment 57655 [details, diff]
Working patch for php-4.3.11
The previous patch was faulty, this is the correct one.
Still no workaround for the SRC_URI problem.
Right now we have #74552, #74880 (this one) and #89155 open basically for the same issue. Would someone look into this and fix the eclass, *please*. Thanks. I agree that both this bug and #89155 cover the same problem; Bug #74552 is the same for php-5, which uses its own eclass, AFAIK. And it is really annoying to see these bugs unfixed, mainly because this is also a security problem. Right now, there is a useflag which should make a php installation more secure. But the ebuild/eclass (almost) silently fails to apply the patch and installs php anyway. (This could be fixed by using 'epatch ... || die' but that belongs into another bug, one yet to be filed. :) ) The php-sapi.eclass now has support for Hardened-PHP for PHP versions 4.3.9, 4.3.10, and 4.3.11. |