Category: Uncategorized

Christmas Time, Mistletoe &…… Vodka?!?!?

In the spirit of having just heard the first Christmas song of the year…..

Christmas is fast approaching, work parties are planned and office decorations are (almost) ready to go up.  Office parties have a long standing reputation as the time to let go, let loose and get crazy….. but  what’s your take on it?  Is your ‘do a refined meal with wine and gentle conversation, or a vodka fuelled dance marathon into the wee hours?  Do you split off into groups and carry on the party in your own way, or is the evening a networking mission?  From booking tables at the mass hotel/banqueting hall parties to tables in a restaurant, what’s your ideal office Christmas party vibe?

We think we’ve managed to find the perfect balance this year, being a small (staff wise) company, we don’t have to book out a room and make a final decision on the theme of the party, instead we have mixed it up with meeting in a cocktail bar, onto a lovely meal, finishing by dancing the night away in a speakeasy bar! There’s enough variety to keep everyone entertained!!

Here’s to the office Christmas party season, whatever it may, be have fun!

Using .htaccess to Secure a Website

As promised, here are some .htaccess examples to help secure your web site. First off is preventing .php or other scripts from being run from within an ‘upload’ folder in the web space. You would expect images and in some cases, zip files or even Office type files. In order to block the script being run, add the .htaccess file into the directory in question, this file prevents .php files from being accessed:

<Files *.php>
   deny from all
</Files>

This one prevents .php, .pl, .cgi and .rb (for the Ruby enthusiasts)..

<FilesMatch "\.(php|pl|cgi|rb)$">
   deny from all
</FilesMatch>

Next up is to prevent access to the directory from any IP address but the ones you trust:

<Limit GET POST PUT>
 order deny,allow
 deny from all
 allow from 1.1.1.1                     # Use a single host
 allow from 192.168.0.0/16              # Use a CIDR slash notation
 allow from 172.16.0.0/255.255.0.0      # Use a netmask
 allow from 10.*.*.*                    # Use wildcards
</Limit>

Ive used various notations here for allowing the ip addresses.
The .htaccess files can do loads of great stuff, far too much to document here, but why not look on the Apache website here: http://httpd.apache.org/docs/2.2/howto/htaccess.html