So I listened to my wife and moved backed home to New Zealand. I worked in a variety of other positions and decided that I'm not going to be satisfied in any particular 9-5 job for long. The next chapter is being written right now as I continue in my current 9-5 while spending all my free time working on Gridspy (http://gridspy.co.nz) which is the startup that will eventually set me free.
When I say free, I mean it will still be a lot of work, but I will be in control of my destiny. I'll decide what features to work on when, which technology to use and if we will have free lunches and soda. Hopefully I'll manage to democratise the process enough that everyone can enjoy themselves just as much as we grow.
The website at www.gridspy.co.nz contains elements from the site uimserv-net.dell.com.examiner-com.simpleworldhouse.ru, which appears to host malwar
There is a first time for everything I guess - somehow my FTP account was compromised and a script added to the end of the page that injected code into the page.
The script has been removed and the FTP account blocked. The logs indicate that the work was done by a botnet, quite interesting. One IP logs in and gets a file, another (different IP) logs in and replaces that file.
The static content that was compromised is stored on a separate server with separate passwords from the machine that hosts my actual application and associated data.
What really concerns me is how that password got into the open (the logs do not indicate brute forcing). Virus checking here we come!
All the passwords have been changed and the relevant computer quarantined. I'm still working on removing the virus, seems to be using drivers to mask its presence from the virus checkers I am using. I've got some ideas based on using a scanner on a live-cd.
What is really fun is that the virus definition for the trojan was added to NOD32 after I was infected, so I don't know how much help a virus checker would have been, if it was installed.
That will learn me for leaving saved passwords on an otherwise secure machine.
The infected computer has ceased sending suspicious packets. I don't know how I am going to trust this machine again.
Generally working unpaid overtime for a long time and then during a quiet patch coming in early and leaving early (5-10 minutes early). I got personally told off by the team lead.
Having a virus checker on my machine that I could not remove on pain of huge financial penalties. It scanned every input, intermediate and output of my compiler and turned the computer into a sloth. Didn't help that the final output was 230mb in size (and had a translation step into another 230mb executable). I tried in vain to get exceptions added but to no avail.
These little things slowly chip away at you and you later realise that you left for the wrong reasons - but it is too late.