To change it:

• Log into the WP dashboard,
• Up in to top right where it says ” Howdy, USERNAME” click that
• Then Network Admin
• Goto Sites on the left
• “Edit” the blog you want to adjust
• Click the “Settings Tab”
• Scroll to the bottom and adjust “Site Upload Space Quota”.
• Click “Save”

Firstly I needed to be realistic this blog wouldn’t have more than two simultanious connections at once, with that known I could then edit the amount for apache server threads to an un-godly small number in /etc/apache2/apache2.conf

<IfModule mpm_prefork_module>
StartServers          2
MinSpareServers       2
MaxSpareServers       2
MaxClients            20
MaxRequestsPerChild   0
</IfModule>


With that noted a quick look at ‘top’ shows MySQL eating lots of Virtual Memory a quick swap of the configuration file: /usr/share/doc/mysql-server-5.1/examples/my-small.cnf to /etc/mysql/my.cnf sorts out that problem. (Don’t forget to backup your originals)

And finally modifying the WordPress max memory limit as noted in this post
suhosin[10882]: ALERT – script tried to increase memory_limit to 268435456 bytes

Anyway I had trouble getting permalinks working and knowing nothing about them I set off in my investigation. It appears that permalinks require mod_rewrite to be enabled. After checking in mods_avaliable and search debian repos, I came up blank. It seems that you need to enable mod_rewrite via the command [code] a2enmod rewrite [/code]

Too Easy!

vps suhosin[10882]: ALERT – script tried to increase memory_limit to 268435456 bytes which is above the allowed value (attacker ‘MY.IP.ADD.RESS’, file ‘/var/www/blog/wp-admin/admin.php’, line 109)

When trying to access parts of the WordPress dashboard. The required fix was that WordPress wanted 256MB of memory (which I didn’t have).

The fix involved editing: wp-includes/default-constants.php
line 28: define( ‘WP_MAX_MEMORY_LIMIT’, ’256M’ );
to something a little more reasonable like 64M

Imagine this scenario: An attacker somehow breaches your network and they have admin rights on a workstation / laptop from the business, now with command prompt access they are able to start a Soft Access Point (WPA2 password enforcement required by Windows 7). When this happens no prompt is given to the user and concurrent access is also maintained to active connections (even from the same wireless adapter which is now hosting our network ), therefore not providing the user with any hint that a problem(?) is afoot.

Now what happens next is limited to the attacker,but perhaps the original method of compromise  get patched so access is no longer available but because a wireless connection being available they still a permanent backdoor with network level access!

Perhaps a good party trick would be to run a script on every PC / Laptop within the business and turn this feature on?

Anyway here is the command:

C:\Windows\system32>netsh wlan set hostednetwork mode=allow ssid=SomeSSIDYouLike key=Some8CharPlusPassword
C:\Windows\system32>netsh wlan start hostednetwork

Happy Internet Connection Sharing!