Hoshino Lina (星乃リナ) 🩵 3D Yuri Wedding prep!!!

Is there some easy/reliable UDP/datagram security layer I can use from Rust? Something simple, shared keys or pub/privkey auth (both directions). If there's nothing better I'm tempted to take wireguard-rs and just remove the routing/tun part...

📢 You can Just Use Rust and Stop Getting Pwned 📢 Node -C +🦀 = node2shell fixed: git clone github.com/hoshinolina/... && cd rust-brotli-decompressor/c && make && cp target/release/libbrotli_decompressor.so /lib64 && ln -nsf libbrotli_decompressor.so /lib64/libbrotlidec.so.1

And yes, I verified that node is really calling into the Rust Brotli decoder in my system. YMMV on other builds of Node. Python usually uses static libbrotli and this would not fix that one, you'd have to link it against the Rust version explicitly.

📢 You can Just Use Rust and Stop Getting Pwned 📢 Node -C +🦀 = node2shell fixed: git clone github.com/hoshinolina/... && cd rust-brotli-decompressor/c && make && cp target/release/libbrotli_decompressor.so /lib64 && ln -nsf libbrotli_decompressor.so /lib64/libbrotlidec.so.1

And before I go to sleep: Yes, this PHP vuln is Yet Another Thing That Would Not Happen If It Were Written In Rust.

And I'm going to go further: Knowing what I know about the Linux kernel, I bet it's full of vulns of this shape (OOM -> early ret -> bad state/uninitialized/etc badness). People with tokens, have fun.

Fedora 43 users install these RPMs to fix PHP: koji.fedoraproject.org/koji/buildin... Fedora 44 RPMs will be here in ~15 minutes give or take: koji.fedoraproject.org/koji/buildin... Arch has pushed the fixed packages to mirrors. No word from Alpine yet and I can't hit their git...

Ah yes, the wikis documenting how to update things are all down for updates!

Whaaaaaaaa "The format was different"... people are saying there was a trailing line break in the XML after the epicenter location name. Are DoCoMo parsing XML with regular expressions????????????? www.docomo.ne.jp/info/notice/... 🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️

The extra line break: fixupx.com/looksky495/s...

Whaaaaaaaa "The format was different"... people are saying there was a trailing line break in the XML after the epicenter location name. Are DoCoMo parsing XML with regular expressions????????????? www.docomo.ne.jp/info/notice/... 🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️

Ohhhh hold on, the quake was real but it was faaaar into the ocean and a nothingburger. Did they... miss the P waves, then sensed the S waves up in Hokkaido and misinterpreted them as P waves and therefore thought a Huge One was coming???

Ohh so there were two warnings. The real one and the fake one. 2 minutes apart. That's about as long as it takes for the waves to move the distance. So maybe they DID get the P waves, then when the S waves came, they were incorrectly detected as new P waves for a bigger quake?

WELL THAT WAS SCARY... that's the first time I get a crazy earthquake EEW false alarm that even hit the outdoor PA speakers!

Last time this happened it was an unconfirmed EEW that hit the early-warning apps several years ago (false sensor reading I think), but this time it was on the metro PA and I think cell broadcast? That's going to be an investigation...