Last week the new Ubuntu was released, and I installed it on my workstation without issue. Today I spent some time installing it also on my main web and mail server; the one serving this blog and others. The installation wasn't quite hitch free.
It seems the attack on my server is fading away. I haven't been paying much attention since invoking "HTTPS always" mitigated the POST overloading. The traffic has long been waning from its thousands of visitors and tens of thousands of hits, to its recently low levels, with another drop in the last week or so to hundreds of visitors making thousands of requests per day.
Soon I expect it to have died completely. Still weird that it happened at all, and I still wonder why.
On 17 April Canonical released the latest version of Ubuntu, v14.04, or "Trusty Tahr" if you prefer names. On April 17 I installed the update on my desktop workstation.
At the end of January, there was an inexplicable Denial-Of-Service attack on my server. One of the hosted domains more than the server. An ingeniously simple POST attack (open an HTTP connection, make a POST request, very, very, very slowly dole out bytes) rendered my web server unresponsive. It never crashed, but the pool of workers was occupied enough to stop responding to the few legitimate requests on the server.
I had some things to do at the keyboard, and no one else in the house to interrupt or roll their eyes, so I decided to dig into my Netflix queue and knock off some of the movies no one else would (or should) watch with me. Hot in the queue is Sharknado. I'm a bit of a sucker for shark movies, even the really bad ones. And apocalypse or survival movies, that aren't all about the gore anyway.
There isn't really much need for spoiler alerts as the movie is pretty much exactly as one might expect. The basic synopsis is that a hurricane over the Pacific ocean both pushes sharks inland with its force and scoops some up and flings them through the air, and our intrepid characters try to survive the onslaught in and around Los Angeles.
While looking for something else I stumbled upon something that sparked a query into IPv6 addressing (we all get on those Internet tangents, right?) which led me to a blog post that gave a hint to a way to add IPv6 addresses to my tunnel-provided server.
It's happened a few times that I've (dunderheadedly) reboot this server remotely and it fails to complete. I've figured out why, and created a workaround.