Wedge

I've been using that setup as an alternative to suExec/PHPSuExec (since both haven't received any updates in years) in my new server. Plus [Unknown] recommended a nice permission setup which IMO is fairly logical and I have been using it for well almost a year. Basically, make all the web server files chown'd to site-user:site-user and make the web process run as site-user-www:site-user (user being different and group being same). Then chmod all files which are primarily read only to 640 and the folders which require write to 750/770 (don't remember properly, should be 750), and make sure that these folders cannot execute PHP scripts. That way, all the other user's are completely locked out, and at the same time you don't sacrifice complete access to the files but still lock PHP out enough to maintain control. Plus if someone gets in, they cannot modify a PHP file or run a script and hence run it securely.

I haven't really had a problem with suhosin, but to each it's own. Group/user is more for preventing a site from accessing other site (so one site's weak site weak security doesn't result in all of the sites getting hacked). Plus FPM will make the instance of apache run in that user/group so it doesn't need to be writable by nobody, but only the user of the site itself.

I got no idea as well, that's why I barely passed in my 5 years of French.

Apparently it's to do with preventing piracy. A company convinced the court that blocking these sites (pastebin, vimeo, dailymotion and a plethora of torrent sites) can reduce piracy. Fine, I see some logic in blocking torrent sites, but pastebin, Vimeo and DM are fairly legit video sharing sites...

Ohh....I had completely forgotten about it :P.

It'd be great to have a hook for these 2 functions so that additional fields from member's table can be loaded which may be added by plugins. Even a basic hook would suffice.

Chrome Beta for Android? It's better, still not up to iOS' level.

Nope, there are some extensions that do that though.