kill it!!!

(there are 51 instance of `killall something` in this .so, of which 23 are `killall -9`)

to everybody suggesting other types of derangement: no, please understand, this is _specifically_ crackhead engineering

i was going to register http://crackhead.engineering but it's already gone :(

there's a hardcoded 32-byte AES key the firmware uses to encrypt passwords... except they fucked up (made an array of u32 and not u8) and 3/4 of the key is zeroes

not that it matters a lot given it's hardcoded

vendor pointing at the end of an INI file (clearly containing C source code): indeed... why should I not put something that is _probably_ a CRC-32 here?

🦋 vendor pointing at a C header: "is this an INI file?"

at first i thought that u-boot on this device is uncharacteristically and unexplainably slow at updating from Ethernet, but no, u-boot finishes in like five seconds and then vscode adds twenty more on top

QA is dead

@oscherler yes

if you're wondering, the (fairly useless and clearly untrustworthy) device was put together after the... exploratory surgery. i try to avoid creating more e-waste. i mean it arguably already was when i bought it, but aside from that.

also, it's good practice to be able to put the erased chunks […]

@charlotte can't argue with this now can i

@charlotte ehh, CF is basically ISA which is basically PCIe which is basically NVMe _hits bong_

look at it. this is so upsetting. gaze upon this awful firmware and despair https://upload.whitequark.org/1769145764-bk7252.bin

(this is the version with CRC-16 interleaved. you'll have to deinterleave it yourself to disassemble the bottle cap)