Security

In the first of a series of posts, Tim gets back to basics with WordPress security with his first look at different updating strategies for WordPress, core and plugins.

Tim dissects a recent talk from Steelcon, what went right and wrong.

Why did I move to using Bitwarden from KeePass, was it a headache and was it worth it?

Tim takes a look at the Feitian ePass a hardware security key that he uses in place of Google Authenticator on some site.

WordPress 4.0.1 has been released and is a security release, please update your sites as soon as possible, want to know why? Well watch as Tim explains why you should be updating right now.

Tim guides you through protecting the WordPress login from brute force attacks with a simple program called Fail2Ban and a tiny 3 line WordPress plugin. Before going into some of the more unusual things you can do with Fail2Ban.

Imagine a world without an admin user role, where sites just run themselves and the only users are editors, is this a ultimate utopia or dystopian nightmare? What if we didn’t have users at all, or even an admin interface? Tim pontificates and experiments with “adminless” WordPress sites and finds it’s future mixed.

Recently Google announced that whether a site is running over HTTPS would be considered as a ranking factor, this has sparked a renewed interest in SSL and Tim has been asked lot’s of questions both about terms as well as implementation so decided to put a small guide together, which quickly grew. So consider this an in-depth introduction to SSL.

PGP has been in the news recently thanks to Google, but it’s strange how for something that’s been around over 20 years very few services send encrypted email. This article looks at PGP and how you can use it to encrypt outgoing emails, personal content and almost anything within WordPress.

Writing a post on WordPress security or performance, then why not let me take a look at it for you for free before you publish?