After updating to 2.7 I can confirm that Wordpress Flowplayer does not work with 2.7

Most likely due to hook changes.

I will be publishing an update shortly to correct this.

UPDATE: This was due to a folder permission problem post upgrade, remember to ensure your wp-content dir is at least 711 doh (Also bear with me on the stylings they also broke my theme :-( )

Also please note I am working on integrating flowplayer 3.0.1. into the plugin, as such do not update your plugin from the development respository at this time.

Another annoyance caused I suppose in an attempt to stop new linux users obliterating their installations within 5 minutes of install …

I liken this to shouting widly at someone jamming their hand in a furnace wondering how long before the smell of burning flesh awakens them to the fact they are being just plain stupid …

seems in this case the developers of RedHat and by extension CentOS have taken pity on what must be the “one armed masses” and started handing out the equivelent of “easy bake ovens” …

cp -rf /src/folder/* /dest/folder/
cp: overwrite `/dest/folder/index.php'?

Now the -f (force) flag should copy without prompting, it’s the sysadmins equivelent of shouting at the bloody thing, but then the people with the “easy bake ovens” are at play and given this command the equivelent of “clippy” poping up asking are you sure with every censored copy, the reason it is still prompting is due to an alias …

[root@test_srv /src/folder]# alias
alias cp='cp -i'

What genius decided to make an optional flag run by default ?

-i is ‘interactive’ aka ALWAYS PROMPT, and evidently overrides -f

To remove this:

unalias cp

And if you’re really paranoid, to put it back:

alias cp='cp -i';

Due to the security issues with wordpress pre 2.6.5, I have deleted all registered users.

All the accounts were registered around the same time, and had never been logged in to.

So please re-register if you are a genuine user.

Cheers

Buzz

Well I have managed to plug the security hole, and I am currently working on refining the deployment by using the ability to disable functions in php …

The downside?

Some 5244 approx functions over 23 a4 pages …

update 04/12/2008:

For the impatient you can grab a php script I have written to build the complete comma separated list from subversion here: https://svn.blog.oneiroi.co.uk/branches/zen_of_secured_shared_hosting/trunk/disable_functions_string.php

Please note this is a ‘paranoid’ list (some 354 functions!), you will need to for instance remove phpversion, ini_get and http_build_query from the list to get wordpress working.

Customize to your needs :-)

This series is officially on hold until further notice,

I have found a serious security bug in the method I was using the deploy suPHP and lock down the environment.

Until I have found a solution to this, I will not be publishing the method of suPHP’s deployment, the bug itself is a very obscure but serious one, which of course makes it all the harder to fix.

Information on the bug once a fix is deployed.

Cheers

Buzz