Remotely Unlocking An Encrypted Hard Disk

Can you remotely unlock an encrypted hard disk? [Jyn] needed to unlock their home server after it rebooted even if they weren’t home. Normally, they used Tailscale to remote in, but you can’t use tailscale to connect to the machine before the hard drive decrypts, right? Well, you can, sort of, and [Jyn] explains how.

The entertaining post points out something you probably knew, but never thought much about. When your Linux box boots, it starts a very tiny compressed Linux in RAM. On [Jyn’s] machine using Arch, this is the initramfs.

That’s not news, but because it is an actual limited Linux system (including systemd), you can add tools to it. In this case, adding dropbear (an ssh server) and Tailscale to the limited boot-time Linux.

Continue reading “Remotely Unlocking An Encrypted Hard Disk”

Linux Hotplug Events Explained

There was a time when Linux was much simpler. You’d load a driver, it would find your device at boot up, or it wouldn’t. That was it. Now, though, people plug and unplug USB devices all the time and expect the system to react appropriately. [Arcanenibble] explains all “the gory details” about what really happens when you plug or unplug a device.

You might think, “Oh, libusb handles that.” But, of course, it doesn’t do the actual work. In fact, there are two possible backends: netlink or udev. However, the libusb developers strongly recommend udev. Turns out, udev also depends on netlink underneath, so if you use udev, you are sort of using netlink anyway.

If netlink sounds familiar, it is a generic BSD-socket-like API the kernel can use to send notifications to userspace. The post shows example code for listening to kernel event messages via netlink, just like udev does.

When udev sees a device add message from netlink, it resends a related udev message using… netlink! Turns out, netlink can send messages between two userspace programs, not just between the kernel and userspace. That means that the code to read udev events isn’t much different from the netlink example.

The next hoop is the udev event format. It uses a version number, but it seems stable at version 0xfeedcafe. Part of the structure contains a hash code that allows a bloom filter to quickly weed out uninteresting events, at least most of the time.

The post documents much of the obscure inner workings of USB hotplug events. However, there are some security nuances that aren’t clear. If you can explain them, we bet [Arcanenibble] would like to hear from you.

If you like digging into the Linux kernel and its friends, you might want to try creating kernel modules. If you get overwhelmed trying to read the kernel source, maybe go back a few versions.

A Live ISO For Those Vibe Coding Experiments

Vibe coding is all the rage at the moment if you follow certain parts of the Internet. It’s very easy to dunk upon it, whether it’s to mock the sea of people who’ve drunk the Kool-Aid and want the magic machine to make them a million dollar app with no work, or the vibe coded web apps with security holes you could drive a bus through.

But AI-assisted coding is now a thing that will stick around whether you like it or not, and there are many who want to dip a toe in the water to see what the fuss is about. For those who don’t quite trust the magic machines in their inner sanctum, [jscottmiller] is here with Clix, a bootable live Linux environment which puts Claude Code safely in a sandbox away from your family silver.

Physically it’s a NixOS live USB image with the Sway tiling Wayland compositor, and as he puts it: “Claude Code ready to go”. It has a shared partition for swapping files with Windows or macOS machines, and it’s persistent. The AI side of it has permissive settings, which means the mechanical overlord can reach parts of the OS you wouldn’t normally let it anywhere near; the point of having it in a live environment in the first place.

We can see the attraction of using an environment such as this one for experimenting without commitment, but we’d be interested to hear your views in the comments. It’s about a year since we asked you all about vibe coding, has the art moved forward in that time?

Bash Via Transpiler

It is no secret that we often use and abuse bash to write things that ought to be in a different language. But bash does have its attractions. In the modern world, it is practically everywhere. It can also be very expressive, but perhaps hard to read.

We’ve talked about Amber before, a language that is made to be easier to read and write, but transpiles to bash so it can run anywhere. The FOSDEM 2026 conference featured a paper by [Daniele Scasciafratte] that shows how to best use Amber. If you prefer slides to a video, you can read a copy of the presentation.

Continue reading “Bash Via Transpiler”

FLOSS Weekly Episode 864: Work Hard, Save Money, Retire Early

This week Jonathan chats with Bill Shotts about The Linux Command Line! That’s Bill’s book published by No Starch Press, all about how to make your way around the Linux command line! Bill has had quite a career doing Unix administration, and has thoughts on the current state of technology. Watch to find out more!

Continue reading “FLOSS Weekly Episode 864: Work Hard, Save Money, Retire Early”

An Event Badge Re-Imagined As A Cyberdeck

We’re used to handheld Linux devices of varying usefulness appearing on a regular basis, but there’s something about the one in a video from [Rootkit Labs] which sets it aside from the herd. It’s a fork of a conference badge.

The WHY2025 badge had pretty capable hardware, with an ESP32-P4, a really nice screen, and the lovely SolderParty keyboard. Here it’s been forked, to become a carrier board for their previous project, the Flipper Blackhat. This is a Linux add-on for the Flipepr Zero, and it seems that plenty of people wanted it in a more useful context. The result is something that looks a lot like a WHY badge, but running Linux.

It’s a great shame when badges end up lying unused after the event, and ones like the WHY 2025 badge are a serious effort to make something that endures. Here, the badge endures in spirit by being forked and re-engineered, and we like it a lot. The full video is below the break.

Continue reading “An Event Badge Re-Imagined As A Cyberdeck”

CPU Scheduler Divines The Will Of The Heavens

Horoscopes are a great way to pass a boring lunchbreak, and an excellent excuse for ending a ill-considered relationship. They’re also a hilarious way to handle CPU scheduling under Linux, thanks to the work of [Lucas Zampieri].

The project is called scx_horoscope, and it’s a sched_Ext scheduler that makes its CPU scheduling choices based on what the heavens are doing in real time. Different tasks are handled based on different astronomical objects. For example, the Sun represents life force, and thus grants boons to key system processes. The Moon, an emotive influence, rules over interactive processes like shells and terminals. Mercury, as the god of communication, handles network and IO tasks, and so it goes from there. It’s not just a surface level thing, either—[Lucas] has implemented the influences of the elements of fire, air, earth, and water, and there are negative timeslice penalties on associated tasks when a given planet lands in retrograde.

You can argue whether or not the broader motions of the heavens have any impact on our lives based on the time and circumstances of our birth. But you can’t argue that scx_horoscope really will influence how your computer runs based on the dance of the planets in the sky. Mostly, though, we concern ourselves with astronomy rather than astrology around these parts!

[Thanks to Benjamin for the tip!]