Moonpig, an online greetings card company suffered a security vulnerability. While the vulnerability was serious, far worse was the company’s deliberately misleading statement in response to the disclosure:
We are aware of claims re customer data and can confirm that all password and payment information is and has always been safe.
— Moonpig (@MoonpigUK) January 6, 2015
Indeed this tiny subset of information was “safe”. What was leaked was all other personal information held by Moonpig about every customer. Much worse than a password or a credit card that can be easily changed. That the company issues a statement like this indicates how little they care about their customers.
Slate is a window management tool for OS X. It differs from most because it’s designed to offer customisation over sensible defaults. In short, to use a hackneyed phrase: a programmer’s window manager.
There are two ways to configure Slate: a declarative way and using Javascript. I use JS, and recently uploaded my configuration to Github. I think Slate’s an awesome tool, so I wanted to go through how I use it.
I’d love to use Docker and, particularly, Fig. The deployment of even this site would be much simpler if I could update individual containers rather than having a somewhat complex set of services running together on a single host.
As of now, however, I’m starting to lose trust in Docker’s security team.
In October, Docker, Inc. announced that version 1.3 of the docker tool would verify container images downloaded from the central docker image repository:
It sill amuses me, the way the iPhone feeds like this amazing tiny iPad when you switch to it after a few hours of reading on the iPad. And for a moment it feels like the iPad must’ve come first, because of that.
The last rewrite of the code which runs this site was in 2009, when I changed from a static site generator I’d written in ruby to an AppEngine site I wrote when I was first learning python. In the main I was very happy with AppEngine: I’d not paid them a cent but they’d happily hosted my site for five years.
Lately, however, I’d begun to want a better understanding of the technologies the site runs on. AppEngine’s abstractions were becoming to much. I’ve wanted a server of my own for a while; I chose Linode (referral URL) because my friends using it haven’t had many bad words to say about it. I chose Cloudant because I work there and wanted to have an app I – sort of! – depend on running there.