diff options
Diffstat (limited to 'src/routes/blog/posts/alpine-ssh-early-initfs.svx')
| -rw-r--r-- | src/routes/blog/posts/alpine-ssh-early-initfs.svx | 69 |
1 files changed, 69 insertions, 0 deletions
diff --git a/src/routes/blog/posts/alpine-ssh-early-initfs.svx b/src/routes/blog/posts/alpine-ssh-early-initfs.svx index a9296b7..1e18126 100644 --- a/src/routes/blog/posts/alpine-ssh-early-initfs.svx +++ b/src/routes/blog/posts/alpine-ssh-early-initfs.svx @@ -11,6 +11,19 @@ updated: "2026-01-14T15:53:57Z" published: false --- +<blockquote class="default-blockquote blockquote-red-400"> + + **Warning**<br/> + This post talks about operations that may lead the reader's system + unbootable, including modifying it's initramfs. + Do not follow along if the reader is not prepared to fix it's own + systems from potentially infuriating bugs. + + <p><small class="text-sm opacity-50 hover:opacity-70 transition-opacity">Maybe avoid following along on the friday + before the reader's vacation.</small></p> + +</blockquote> + For a while, this one's been meaning to setup an early-boot SSH environment for Alpine Linux on systems that are using a [System Disk](https://wiki.alpinelinux.org/wiki/System_Disk_Mode) installation @@ -37,6 +50,62 @@ staying close to the intended upstream Alpine installation Alpine's [mkinitfs](https://gitlab.alpinelinux.org/alpine/mkinitfs/) allows us to do things like including files or kernel modules in the image, via their [features.d](https://gitlab.alpinelinux.org/alpine/mkinitfs/-/tree/master/features.d). + This is nice and all, but on it's own, we can only really give the kernel a module, or a file we manually call by spamming enter through the encryption password prompts and running via the 'Emergency Shell'. + + +### approach 1: patching + +The easiest solution this one thought of was to just directly modify +`/usr/share/mkinitfs/initramfs-init` and be happy, then deal with it when +upstream modifies things. + +This is, however, very not "set, make a blog post, and forget". So we skipped +that idea. + +### approach 2: fork the upstream + +The second, and nicest to upstream solution it thought of was modify +[initramfs-init.in](https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/cc4954bc73cf55833b48624232b9c42ca3abc390/initramfs-init.in) + - which gets built into `/init` in the initfs. + +This would've worked very well, but would require maintaining one's own +`/init`, for which the distro provides few guarantees that the rest of the +tooling will forever accomodate an old version forked off. + +#### upstreaming + +It also thought about upstreaming this, for which this would've been the only +viable approach. However, with this, comes the challenge of cleaning up the +sshd during early openrc, cleanly, without any use-case edge-cases. + +> **For Alpine Maintainers**<br/> +> If beings involved in the mkinitfs project want something like this, this +> one's willing to, with some guidance on avoiding user edge-cases, contribute +> this. + +### approach 3: third approach's the charm + +The third approach was wrapping +[nlplug-findfs](https://gitlab.alpinelinux.org/alpine/mkinitfs/-/blob/cc4954bc73cf55833b48624232b9c42ca3abc390/nlplug-findfs.1.in), +replacing the system-wide binary, regenerating the initramfs, and then spawning +SSH from there and directly interacting via libssh. + +Whilst this would be sensible in theory, this has a high maintenance burden if +nlplug-findfs is modified substantially (or, worse, entirely removed). This is +heavily in no guarantees provided land. + +So this one opted against it. + +### approach 4: a kernel module + +A kernel module could start a userspace process early, which would not involve +touching any of the existing tooling's code (and just needs one file added). + +But also, no. + +## starting ssh before `initramfs-init.in` + +> "it's like LogoFAIL for your initfs" - somebeing, probably |