all 21 comments

sorted by: hot top controversial new old
[–] 3 points 17 hours ago*

Ok gang, I guess we're moving to ms paint 🀷

  • source
  • [–] 7 points 22 hours ago

    They can't keep getting away with this

  • source
  • [–] 18 points 1 day ago* (last edited 1 day ago) (1 child)

    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

  • source
  • hideshow 1 child comment
  • [–] 27 points 1 day ago (1 child)

    Don't even joke, I would not be surprised if our security team latched onto this unironically.

  • source
  • hideshow 1 child comment
  • [–] 63 points 1 day ago
    [–] 14 points 1 day ago (1 child)

    Have you seen what happens why you hit F12 in a browser?

  • source
  • hideshow 1 child comment
  • [–] 33 points 1 day ago

    Fuck that's a lot of critical infrastructure that's vulnerable!

  • source
  • [–] 24 points 1 day ago

    Type slower! That made me laugh

  • source
  • [–] 14 points 1 day ago

    Got me for a second! πŸ˜…

  • source
  • [–] 5 points 1 day ago

    Jokes on you, my server has no terminal, not even a shell (I use Talos, everything is managed via mTLS protected API)

  • source
  • [–] 7 points 1 day ago (2 children)

    Me using HaikuOS and AmigaOS: ha suck it!

  • source
  • hideshow 2 child comments
  • [–] 5 points 1 day ago (4 children)

    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.

  • source
  • hideshow 4 child comments
  • [–] 2 points 18 hours ago*

    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

  • source
  • parent
  • [–] 7 points 1 day ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment