While trying to install a RapidSSL wildcard certificate on our Zimbra 8 server a while back, I ran into some issues while using Zimbra’s zmcertmgr command:

When I began writing this review there had been 921 days since the last stable Slackware release. The apparent dormant state of development raised a few questions about the health of the distribution, but as usual the rumors of Slackware’s decline was greatly exaggerated.

Some unfortunate but understandable news emerged on the Slackware ARM website today as ARM maintainer Stuart Winter released the following announcement:

As a Tor (The Onion Router) user I already have a negative impression of CloudFlare due to their captcha trolling. It therefore gives me no joy to see CloudFlare Always Online circumventing my hotlink protection in order to “cache” my content on their service.

I’m pretty much done with getting annoyed by all the spam and fake applications populating the Chrome Web Store. But still, once in a while you come across something special that is just too good to pass up.

This WordPress blog is now hosted on a Raspberry Pi 3 after a year of running on a Raspberry Pi 2. Unlike with the RPi2, I’ve not done any overclocking on this device. I’m hoping that decision will decrease the number of file system related issues and obscure kernel oopses I’ve experienced lately, but I guess time will tell.

The RPi3 is still running Slackware ARM 14.2 and the Linux kernel is at version 4.4.7 at time of writing.

Let’s get ready to rumble: a battle of two Slackware ARM powered webservers.

Hosting your WordPress installation on a RPi2 can be a challenge on multiple levels. Apart from stability issues, my biggest concern is always subpar PHP performance and additional overhead with TLS connections. To determine the potential gain of upgrading my hosting platform to a RPi3, I’ve done a few tests with a MicroSD card I recently retired due to data corruption.

Since I hit the one year mark today I thought I would do a quick update on my RPi2 project. A short recap to kick things off: the project had a rough start due to some overly ambitious overclocking that eventually resulted in severe data corruption. However, after implementing the necessary modifications I enjoyed close to 300 days of easy uptime before a power failure took the RPi2 down. My initial thought after the power failure was that everything was still dandy, but a few weeks later things started to go downhill fast. It all began with a few file system errors:

So this website was pretty much free of trackers with one notable exception, the fonts provided by the Twenty Fifteen theme. By its use of the Google Fonts API, most visitors were still leaking data back to the great chocolate factory. However, as the fonts are open source we’re free to use them outside of Google’s realm.

‘Tis the season to be cracking.
In the webhosting business we’re used to seeing an increase in attacks during the holidays, as most people by then are busy with real life. If you’re a cracker though, this is your favorite time of the year.