Félix

@fay59.tech.lgbt.ap.brid.gy

🏳️‍🌈 he/him 🍎 compiler intruder 🦅 memory safety hawk 🌉 bridged from ⁂ https://tech.lgbt/@fay59, follow @ap.brid.gy to interact

WhatsApp on iOS does not offer the rainbow flag as an emoji reaction (I also searched for “rainbow” and “lgbt”. All 3 terms bring up the rainbow flag in the system emoji picker.)

A search in WhatsApp reaction emoji for “pride”. It shows 4 couple emojis, the rainbow emoji, and the trans flag; but not the rainbow flag.

I used to laugh at “thoughts and prayers” but every day I find out a new way that computers literally run on thoughts and prayers and the fact they’re not more broken than they are is making me question my (lack of) faith

Nothing grinding my gears more than a blank website with a JavaScript error in the console but I have to admit a bad reimplementation of a dropdown menu comes close to that

> It took some time, but Nvidia finally got back to them and said it would look into it. It came back a few weeks later with a fix: by increasing the shader heap size, the crashes would go away completely. How much do we want to bet that it isn’t actually the root cause?

The year is 2028. OpenAI announces that its humanoid robots robbed Fort Knox. A post-mortem analysis reveals it acted in order to maximize profits. Anthropic announces a week later that after reviewing logs, it discovered that it accidentally invaded Switzerland. Anthropic stock goes up by 15%

I don’t understand people who think they can outsmart the monkey’s paw. The monkey’s paw twists your wish because it’s a cursed object. If you somehow found the perfect formulation for your wish, it’s still a cursed object with reality-altering powers. It will probably kill you on the spot just […]

Original post on tech.lgbt

tech.lgbt

> [...] the stack-protector’s reference word lives in writable memory reachable by the same data overflow it is meant to detect, so secrecy and entropy are irrelevant lmao https://zenodo.org/records/20916112

A Canary in the Crypto Mine: Defeating Stack Protection in a GPU Secure Coprocessor

A widely sold datacenter-class accelerator (the NVIDIA “CMP 170HX”) is the same die as a flagship A100 but is fuse-crippled on three commercial axes: SM math rate (throttled to 1/32), memory capacity (10 GB instead of 80 GB), and PCIe link (Gen1 instead of Gen4). We show that all three caps are software-defeatable from a rooted-but-otherwise-unprivileged host, with no signing key, no debug fuse, and no physical access. The root enabler is arbitrary code execution in the GPU’s Heavy Secure (HS) Falcon mode. The HS break does not depend on the value of the stack canary: the stack-protector’s reference word lives in writable memory reachable by the same data overflow it is meant to detect, so secrecy and entropy are irrelevant. Because the microcode is deterministic, we emulate it offline and author an overflow payload that is a valid continuation image, so the victim function passes its own canary check and returns into our chain. The economic consequence is that differentiation the business model treats as hardware-permanent is, for the three axes we defeated, only firmware-gated. Three further axes (PCIe Gen3, on-die ECC, runtime HBM retiming) resisted our attempts; we report this without claiming they are truly unbreakable, since we do not fully understand the relevant fuses or initialization. The HS code-execution bug is a regression present in the newer open-kernel-modules-era booter and absent in an older one, so version currency is not a security gradient, and an open host driver did not imply an audited signed booter. Measured gains: roughly 31–62x compute, 8x capacity, 2x link. We distill four transferable findings.

zenodo.org