Compromised Server Security Measures

Recently, my employer's web server hosted on Rackspace Cloud was compromised (yes I still have a day job), and I helped resolve the issue, consequently formulating some security measures which I hope to impart today wishing you won't have to go through the upheavels we had. You may also learn more on this from Linux Server Security and Secure Architectures with OpenBSD.

From the experience we had at work, here are some of the measures I would advocate (some advise you may have encountered somewhere else):

• Isolate access to the compromised server
• Secure the workstation that solely accesses the server
• For web application scripts, have trusted copy in version control systems
• Your .htaccess may be the culprit
• Setup routine file change monitor

As our modus operandi goes, below are the rationale and discussion of the measures above.

What a Tablet Computer Could and Should Be

With all the hype over Apple's iPad and the feasibility of having your own custom-made touchscreen tablet computer, I think we deserve a better user experience of how we can acquire and interact with a touchscreen tablet computer (which from here onwards we will refer to as tablet computers to save on tongue twisting effort). We will not discuss the usual desirables, like durable and eco-friendly parts and components, fast responding user interface, smooth graphics, and high fidelity (that's oldspeak for hi-fi) sound, they should be standard features.

Below is a list of proposed improvements every tablet computer could and should have:

• Have Dvorak keyboard layout as option
• Make Internet access via Wi-fi AND Bluetooth easy
• Fast, compact, standard compliant web browser
• Open standard video and audio support
• Text-to-speech book and news reader built-in
• Must be social network agnostic
• Interface port
• No cellular phone capability
• Use BSD operating system instead

Below are the rationale for the proposals we have above.