So my kid's smart baby monitor decided it needed a firmware update at 3 AM. Naturally, because why wouldn't a glowing plastic bear require a full cryptographic signature verification just to stream 480p video of a crying infant. I'm sitting there in the dark, smelling of spit-up and stale coffee, trying to figure out why the bootloader is complaining about a corrupted root certificate. It is a baby monitor, guys. It transmits video of a potato sleeping. Why does it have a more complex secure boot chain than my actual work laptop? I ended up having to serial-interface into this stupid thing just to bypass the signature check because the manufacturer's server was down. Now my baby's crib is technically running a custom build of Debian with a custom kernel just so I can see if he is breathing without walking up the creaky stairs. If someone wants to hack my baby monitor to watch a toddler sleep-kick a stuffed elephant, honestly, be my guest. Just don't wake him up or I will find you and make you explain the concept of naptime to him.