Continuing my long tradition of frequent host changes, this site has been moved to yet another host. In the last few years I’ve used a number of hosts (and there’s a couple more not on that list), and this time I’m taking a bit of a risk – so it’ll be interesting to see how this one works out. I’ve switched to a company called QuickPacket, but this time instead of a fairly beefy VPS, I’ve went in the opposite direction – absolute minimum.
The new plan is about as minimal as it gets:
- 128 MB RAM
- 256 MB vSwap
- 1 CPU Cores
- 20 GB Disk Space
- 500 GB Bandwidth
The upside to this? It’s only $15 per year.
So I’m going to focus on caching and optimization to keep this and a few other sites running on such lean resources. In theory WordPress should be able to do it, if it can’t – I’ll switch to Octopress or something similar.
This should be a fun challenge.
Wow! It’s been over a year since this blog o’ mine has seen any activity, though I’ve certainly not forgot about it. A lot has happened in the last year, so I’ll use this post as a bit of an update (and a warm-up for my return to blogging).
I’m not going to promise you’ll see a new post daily as was once the case, though I’ll try to ensure something new is up at least once a week.
Yesterday the news hit of a new vulnerability that threatens the security of all code; dubbed Trojan Source by the researchers from the University of Cambridge. From an initial analysis, it does seem to impact just about everything, and the status of fixes is very hit or miss at this point. But the real question is, does this even matter? Is this issue worth spending your time on? Let’s look closer.
During my Christmas vacation last year, I converted this site from WordPress to Hugo; while I’ve been happy with the change, a couple of features are missing. One of these is that there was a section with related content at the bottom of each post. I wanted to get it back.
Thankfully Hugo has native support for Related Content, so while I was hoping this would be a simple task, there’s a note that made things substantially more complicated:
It’s time for everyone from the industry, developers, and the government to declare war on ransomware and make it as hard as possible for them to ply their insidious trade. There have been false starts and baby steps, diligent fighters without enough resources, and vendors that have only given a nod to the issue. It’s time to use every tool reasonably available to stop this scourge.
For so many in the industry that have dedicated so much of their time and effort to this fight, this statement may seem to diminish their efforts, but that is not my intent.
Over the last year or so, I’ve become quite a fan of Air Disasters, a television show dedicated to analyzing plane crashes and similar incidents. As I watched the show, I started seeing many ways that the lessons and procedures around aircraft safety also apply to running a security team; this valuable and hard-won wisdom, often born out of tragedy, can be of significant impact if appropriately applied. In this article, I will explore Crew Resource Management and how it can be applied to Information Security to make teams run better.
