Make test failed about suhosin

[ck-on]

@RoderickVincent for what it's worth mine fails that test too but it looks like you passed with flying colors otherwise.

Note that option is off by default anyway in suhosin, in theory you should be just fine.

[rlindsberg]

Thank you for your reply! But I don't quite understand what you are talking about. Do you mean that you did a test and encountered such the same error like me? And do you know where is the problem?

Yours sincerely

Roderick V.

Semlaland.com Affordable as well as Premium shared web hosting. Proudly made in Jönköping
Cassie.in Fashion House, personal blog & more!

On Jul 25, 2014, at 20:23, "ck-on" [email protected] wrote:

@RoderickVincent for what it's worth mine fails that test too but it looks like you passed with flying colors otherwise.

Note that option is off by default anyway in suhosin, in theory you should be just fine.

—
Reply to this email directly or view it on GitHub.

[stefanesser]

What he means is that for some systems there are far more tests failing. However we detected that for some tests the test fails just because the error message is printed in an unexpected position of the output. So it might be just a stdout/stderr buffering problem on different operating systems. We will try to fix that with the next real release.

When you report a failed test please paste the output of the various error files created by failing tests like:

tests/filter/suhosin_upload_disallow_binary_on.diff

[rlindsberg]

Thanks. Here is the content of that file:
458+ e dropped (attacker 'REMOTE_ADDR not set', file '/home/Ella/suhosin-master/tests/filter/suhosin_upload_disallow_binary_on.php')461- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')462- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')463- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')464- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')465- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')466- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')467- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')468- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')469- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')470- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')471- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')472- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')473- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')474- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')475- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')476- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')477- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')478- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')479- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')480- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')481- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')482- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')483- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')484- ALERT - uploaded file contains binary data - file dropped (attacker 'REMOTE_ADDR not set', file '%s')

[szepeviktor]

I have problems also
Debian GNU/Linux 7.6 (wheezy)
systemd
PHP 5.4.31-1~dotdeb.1 with Suhosin v0.9.34-dev MAYBE this is the problem?
gcc-4.7.real (Debian 4.7.2-5) 4.7.2

as root

Testing: suhosin.executor.func.blacklist=printf [tests/executor/function_blacklist_printf.phpt]
Testing: suhosin.executor.func.whitelist=call_user_func [tests/executor/function_whilelist_call_user_func.phpt]
Testing: suhosin.upload.disallow_binary=On [tests/filter/suhosin_upload_disallow_binary_on.phpt]

as user

Testing: suhosin.executor.func.blacklist=printf [tests/executor/function_blacklist_printf.phpt]
Testing: suhosin.executor.func.whitelist=call_user_func [tests/executor/function_whilelist_call_user_func.phpt]
Testing: suhosin.upload.disallow_binary=On [tests/filter/suhosin_upload_disallow_binary_on.phpt]
PHPSESSID session id not too long [tests/session/PHPSESSID_max_id_length_ok.phpt]
session id not too long [tests/session/max_id_length_ok.phpt]

Please advise.

[bef]

In Linux tests appear to truncate printf() output with suhosin.log.stdout exceeding a certain length. As warning messages in suhosin contain the full path of the php file, this behaviour can be reproduced by testing with a long path name (e.g. ridiculously long /home/user/_src/suhosin). On the other hand, a very short path name (e.g. /tmp/s) should let all test cases pass correctly.

The idea behind suhosin.log.stdout is that suhosin warning messages are not randomly mixed with the test case's output, e.g. var_dump() with WARNING lines in between the lines. This behaviour was seen before, when test cases logged to stderr and PHP's run-tests.php automatically merged stdout and stderr.

Any ideas on how to resolve this Linux specific issue would be greatly appreciated.