Ok gang, I guess we're moving to ms paint π€·
post
They can't keep getting away with this
Saw this scrolling All, took me a sec (it's early am). Just about shat meself, i just finished fucking patching 350 deb boxes for the goddamn PHP cve and CA debacles
Don't even joke, I would not be surprised if our security team latched onto this unironically.
Have you seen what happens why you hit F12 in a browser?
Jokes on you, my server has no terminal, not even a shell (I use Talos, everything is managed via mTLS protected API)
Me using HaikuOS and AmigaOS: ha suck it!
This does however make me wonder if it's possible to interact with a Linux system without first logging in. Some bootloaders have a shell and I think there's also a UEFI shell? No idea what they are capable of, though.
Well that is exactly what chroot'ing is, loading up another linux instance so you can modify the local (usually broken) one
This is intentional behavior as you need physical access to the drive, and most sensitive information is either encrypted by your application(keyring, password manager, password protected files, etc), or you can choose to encrypt your whole drive
Not directly. UEFI itself only supports mounting a minimal set of filesystems. That's why your EFI system partitiion needs to be FAT32, for example, and why the kernel and initial ramdisk are also located there. UEFI mounts the ESP and executes the bootloader, which then loads the kernel (located at ESP/vmlinuz-linux on Arch) and initial ramdisk (ESP/initramfs-linux.img) into memory. The initial ramdisk is a compressed image of an early root filesystem that contains the tools and drivers necessary to boot the full system, including the filesystem drivers for ext4/btrfs/whatever.
You could build an EFI program that natively supports different filesystems, though.
I mean you can easily edit grub at boot and boot straight into single user mode without logging in.

all 21 comments