In the last few days I’ve noticed a few unusual GET requests for supposedly exposed SSH private keys. All requests are following the same pattern:

This website recently celebrated its second year of Raspberry Pi based hosting. It’s currently running on a RPi3 with Slackware ARM 14.2 (32-bit soft float). Somewhat to my surprise, the second year went by without a single glitch.

In a time-frame of just 10 seconds I got 1200 requests from the Jorgee vulnerability scanner, originating from 15 unique IP addresses. As usual it was just a blind attack probing a /24 subnet.

When you’ve been running GNU/Linux distributions for an adequate number of years, I do believe you’ll eventually find yourself walking the path to Mount Gentoo in hope of joining the ancient Greybeards. Many have met their demise on the road ahead, but armed with the Gentoo handbook we’re confident that it’s within our reach.

My office workstation recently went trough a Slackware release upgrade by following the excellent systemupgrade article from the Slackware Documentation Project. Personally I experienced a few snags along the way so I’ll add a few notes for future reference.

Time for another unfortunate run in with the OTRS 5 Daemon. Again I got a call from a customer informing me that OTRS had been idle for a day without creating any new tickets.

Building the latest Hugo release from AUR (Arch User Repository) fails with the following error message:

A few weeks back I got a call from a customer who complained that OTRS had been idle for a day without creating any new tickets. After some initial troubleshooting it became clear that OTRS was simply no longer able to retrieve mail.

Disclaimer: this is a minimal approach bereft of automagic and thus likely not desirable for most users.