On Wed Jan 21, 2026 at 4:12 PM GMT, Jonathan Dowland wrote:
On Wed Jan 21, 2026 at 1:21 PM GMT, Gareth Evans wrote:
Can anyone reproduce this behaviour, or have any suggestions?
I'll have a go at reproducing Today or Tomorrow.
This is a shallow test: I didn't regenerate my initramfs first, but I
(by coincidence) had to cold boot my desktop, so I gave it a go. I was
able to SSH in and run cryptroot-unlock successfully.
dropbear-initramfs:
Installed: 2025.89-1~deb13u1
Linux 6.16.9+deb14-amd64 #1
/etc/dropbear/initramfs/authorized_keys contains two entries, labelled
jon@phobos and jon@qusp (the latter of which my client issued)
The server does not have a /root/.ssh/authorized_keys so the initramfs
has not picked it up from there (unless there's another place it could
be hidden)
My initramfs dates from:
-rw------- 1 root root 129582334 Jan 11 14:36
"/boot/initrd.img-6.16.9+deb14-amd64"
I'd wager that was triggered by installing 2025.89-1~deb13u1.
I'll try regenerating it later and see what happens.
--
Jonathan Dowland
[email protected]
https://jmtd.net
