Sorry to be always posting these "Anyone use such and such on shared hosting servers?" But it's pretty much the best thing I can think of instead of experimenting and going through all problems myself first. I guess all of us likes to see someone else try something out first and give feedback on it before attempting to implement himself.
I want to try this GreenSql as a way to help prevent user's web apps from being hacked using sql injection. Ive tried suhosin sql protections in the past but they simply don't work, but there is no kind of docs or even simple explanation anywhere about it on hardened-php site so that's probably why.
If anyone here uses this, has used it and knows anything about using this on a shared server please share your experiences. I am going to implement it on a test server no matter what but would be nice to know that this isnt one of those things with insane default rulesets.
It looks real cool and I will be giving it a try myself probably tonight and tomorrow. If anyone is interested I will post my findings.
As the rest of you hosts know we cannot guarantee 100% security or any kind of hack proofness. But in my time I have found out taking some steps to help preventing weak and outdated php apps can help in preventing disgruntled wep-app-hacked clients from making a crusade on the web saying you servers are insecure, crappy and all that. Isn't a sure fire way but I think it helps.
So something like this can only help in that situation.