With the end of the advent, this years sysadvent calendar event is now over.

If you missed it, the articles are still over at the sysadvent microsite. This year, the advent calendar consisted of the following articles:

2016-12-01: Grooming your SSL/TLS setup with cipherscan

2016-12-02: Liberating the network

2016-12-03: Publishing Jekyll updates with gitlab-ci

2016-12-04: PaaS Play

2016-12-05: Adventures in bash - catching several exit values in a piped set of commands

2016-12-06: Spicing up your own access with capabilities

2016-12-07: Using systemd timers

2016-12-08: Elastic Stack

2016-12-09: Slimming down the Internet routing table

2016-12-10: ncat, a modern implementation of netcat

2016-12-11: Read logs in powershell console

2016-12-12: Serving a static website from bucket storage

2016-12-13: Bash: Random numbers for fun and profit

2016-12-14: Use virt-manager to build disk-images

2016-12-15: Securing the Elastic Stack

2016-12-16: Pros and cons of visualizing firewall activity

2016-12-16: Fun with firewall activity plotting

2016-12-17: JMole monitoring framework

2016-12-18: Deduplication of old filesystems

2016-12-19: Small-scale honeynet with Raspberry Pi

2016-12-20: Enabling HTTP/2 for a site

2016-12-21: Feeding the Elastic Stack

2016-12-22: Systemd at 3am

2016-12-23: Encrypted cloud backups with Duplicity

2016-12-24: Running wallscreens using a Raspberry Pi

We hope you enjoy the articles!

Lars Olafsen

Operations Manager at Redpill Linpro

Lars has been in the IT business for around two decades now, working initially both as a developer and systems administrator. He's been with Redpill Linpro for 9 years, and in addition to being one of our operations managers, he still gets the time to solder together pieces of code.

Validating SSH host keys with DNSSEC

We have all done it. When SSH asks us this familiar question:

$ ssh redpilllinpro01.ring.nlnog.net The authenticity of host 'redpilllinpro01.ring.nlnog.net (2a02:c0:200:104::1)' can't be established. ECDSA key fingerprint is SHA256:IM/o2Qakw4q7vo9dBMLKuKAMioA7UeJSoVhfc5CYsCs. Are you sure you want to continue connecting (yes/no/[fingerprint])? 

…we just answer yes - without bothering to verify the fingerprint shown.

Many of us will even automate answering yes to this question by adding StrictHostKeyChecking accept-new to our ~/.ssh/config ... [continue reading]

Single node Kubernetes setup

Published on April 04, 2019

Configure Alfresco 5.2.x with SAML 2.0

Published on March 25, 2019