Page 1 of 1

PHP with Suhosin and Imagevue X2

Posted: 23 Jan 2009, 18:03
by Nick
Suhosin is a 'hardened php' project, and is appearing on some servers causing errors with upload, authorization and such. And we finally tagged it with 'unusable'.

But I bought some server space on slicehost.com to do some dev, and guess what?

PHP Version 5.2.6-2ubuntu4
This server is protected with the Suhosin Patch 0.9.6.2
Copyright (c) 2006 Hardened-PHP Project

So, Imagevue X2 works with Suhosin if everything is properly configured on server. I uploaded, chmodded content/ and imagevue/config and it worked right out of the box. While displaying suhosin incompatibility icon in the corner.

Authorization, upload, and config editing work fine.

Posted: 02 Oct 2009, 15:42
by sigma
My hosting tech support has indicated that suhosin is disabled by default. I just updated to the latest version and thought I did everything right but I cannot edit my admin settings and I get two warning icons at the top right of the admin page. one for EXIF info and the other for suhosin problems. I asked my hosting provider to place a php.ini file in the imagevue directory but it caused a network error, like a 500 or 404 type error.

I'm running out of ideas. What do i have to do to get my admin settings to hold? I edit them and save, but they keep bouncing back to default.

Posted: 04 Oct 2009, 09:42
by mjau-mjau
Nick will have to answer this, but just out of the blue - Did you try clicking the TOP "save" button instead of the bottom one when editing your settings?

Posted: 04 Oct 2009, 10:39
by sigma
omg no! i just tried it and presto! settings saved. I didn't notice it there. I guess I'm conditioned to look for a save button at the bottom of the page.

Thanks!

My problem is that.....

Posted: 16 Nov 2009, 11:42
by KIKKO
My problem is that..

my hosting service support have made some changes:
From
php_admin_value suhosin.request.max_vars 100
php_admin_value suhosin.post.max_vars 100

to
php_admin_value suhosin.request.max_vars 500
php_admin_value suhosin.post.max_vars 500

That' s why my gallery it's not working. My imagevue version is 2.1.5
Admin panel is working, but gallery not.

what can i do ?

Sorry for my english :oops:

KIKKO

I forgot to tell you that...........

Posted: 16 Nov 2009, 11:46
by KIKKO
The hosting server properties :

This program makes use of the Zend Scripting Language Engine:
Zend Engine v2.2.0, Copyright (c) 1998-2009 Zend Technologies
with eAccelerator v0.9.5.3, Copyright (c) 2004-2006 eAccelerator, by eAccelerator
with Zend Extension Manager v1.2.2, Copyright (c) 2003-2007, by Zend Technologies
with Suhosin v0.9.29, Copyright (c) 2007, by SektionEins GmbH
with Zend Optimizer v3.3.3, Copyright (c) 1998-2007, by Zend Technologies

Posted: 17 Nov 2009, 01:23
by Nick
I see they threw everything they could in the mix of worst.

1. Make sure you're having the latest 2.1.6 release which has a workaround for eAccelerator
2. Try the trick with .htaccess to disable Suhosin like it said below here:
https://www.photo.gallery/v2docs/troubleshooting
try to add this .htaccess to your site:

php_flag eaccelerator.enable 0
php_flag eaccelerator.optimizer 0
3. If nothing helps - get back to me with ftp login to your site.

Re: PHP with Suhosin and Imagevue X2

Posted: 04 May 2013, 07:14
by Bulletproof IT
Hi,

Why is this still a sticky? It's dated JAN 2009 - 4 years ago!

Has nothing been done to resolve thumbnail creation and other errors and alerts (as mentioned above) to resolve this?

I too get a "SUHOSIN installed.... hardened PHP project". I have ZERO issues with other scripts that perform image resizing, EXIF extraction, and many other tasks!

I'm confused why this is still an issue, why there is no formal documentation to resolve it and why I am being alerted of SUHOSIN? What I can do about it?

Thank you very much for your time.

:)

Re: PHP with Suhosin and Imagevue X2

Posted: 05 May 2013, 12:46
by Nick
If everything works - just disregard it. I guess we should remove this warning since PHP goes with suhosin by default now.

Back then when we added this, there was a rise of servers where admins were tightening nuts and bolts so hard the uploader didn't work.