It’s become somewhat of a tradition to do a PHP version round up at the end of the year. In 2014 Anthony Ferrara posted PHP versions in the wild and last year I continued the tradition (with his blessings) with my PHP version roundup post. This is a continuation of that post.
In this post I’ll be detailng:
patch version fragmentation % change in install numbers % of installations running an insecure or out of date PHP version.
This is a quick code dump post to share a script for automating LetsEncrypt certificate renewals for my blog!
What is LetsEncrypt? LetsEncrypt is a certificate authority who’s goal is to provide free certificates to help encrypt the web! It’s backed by well known internet and privacy organisations such as EFF, Mozilla, Akamai and Cisco.
My blog uses a continuously renewed LetsEncrypt certificate using AWS CloudFront and S3 and deployed using Codeship during my existing build process for developerjack.
Last year, Anthony Ferrara posted an excellent round up of PHP versions in the wild, specifically focusing on the volume of un-patched versions running production websites. Even as an estimate it was an eyeopening moment for many people.
12 months on I’ve reproduced this report focusing on:
patch version fragmentation % change in install numbers % of installations running an insecure or out of date PHP version. Introduction Methodology Matching Anthony’s approach, data is taken from w3techs.
I recently went through the process of relocating my DSL service (I know I know - it’s not cable or NBN, but hey, I barely use it!) Two days after my seemingly flawless account update, I received a text message on my phone, and thus begins my rant on passwords, protocols and publicity.
My story begins when I received my new account password by SMS, along with my username, and the provisioning date.