[TYPO3-dev] typo3 and PHP 5.3.2

[Enrique Mabanza]

Thanks, for your answer!
So, our current solution seems to be a reasonable thing to do at the moment.

Concerning the creating of the bug report I do have to admit, that I
am not sure what to put in there nor do I see a button that allows me
to enter any information. Therefore I shall leave this to someone more
knowledgable and able as I seem to be at the moment.

Thanks everybody, and keep up the good work!

Enrique

2010/3/24 Dmitry Dulepov <dmitry.dulepov at gmail.com>:
> Hi!
>
> Enrique Mabanza wrote:
>> When I do that, I get this (apart from lots of other stuff):
>>
>> [SCRIPT_FILENAME] => /users/dangast/www/typo3/index.php
>> [SCRIPT_NAME] => /typo3/index.php
>> [ORIG_SCRIPT_FILENAME] => /users/dangast/core/php
>> [ORIG_PATH_TRANSLATED] => /users/dangast/www/typo3/index.php
>> [ORIG_SCRIPT_NAME] => /binary-exec/php
>
> Seems like you have fcgi or something like that. I never used this (I
> prefer Apache module), so I am not sure how this should work. In any
> case these "ORIG_" variables for some reason point to PHP binaries
> instead of files.
>
> The only solution I can propose is to patch files manually and submit
> the information to the bug tracker. As soon as more people start to
> upgrade to 5.3.2 we may gather some statistics and change TYPO3 if it is
> indeed a TYPO3 problem.
>
> Could you create a bug report and out information about these variables
> there, please?
>
> --
> Dmitry Dulepov
> TYPO3 expert / TYPO3 security team member Read more @
> http://dmitry-dulepov.com/
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev
>