Hacker Dudes// alternate deck. same feed.
FEED ~11/h Δ0 ────:──── LINK ░ SIGNAL
99%
SPOOLED 0/45 CYCLE 61339.949.164.24
Bye Bye Brotli? Google's Compression Library Is a Security Messbugsink.com
31pts/7 comments/1d/─
by vanschelven / hn> / « feed
▲▼ vanschelven11:08 hn>

Author here, happy to discuss.

I also constructed (with agentic help) this absolute mess of a timeline (linked in the article, but I think interesting on its own):

https://www.bugsink.com/blog/http2shell-timeline/

▲▼ galadran14:40 hn>

Something that has flown under the radar and is missing from your timeline: https://bugzilla.mozilla.org/show_bug.cgi?id=2029458

▲▼ galadran14:42 hn>

Fx independently discovered the RCE which Google had silently patched and flagged it in April.

▲▼ vanschelven15:30 hn>

Wow it's even more insane than I thought. That actually expands into 3 more relevant dates, all of which I've added to the timeline.

▲▼ mplantsheer16:27 hn>

Thanks for the timeline!

▲▼ runningmike11:44 hn>

Source https://github.com/google/brotli for who wants to do a real security audit.

Security is always context dependent. For many use case it works. But if any one knows a better alternative that is battle tested and used please shout out!

▲▼ vanschelven12:04 hn>

I don't know what a "real security audit" is in this context but I think I shared enough pain (with links) from my personal perspective to give a head start I suppose.

I agree security is always context dependent but "passes untrusted input through a package built in C which takes over a year to make security releases when the changelog already references those" makes the set of contexts in which something passes the test very small

One better alternative is presumably the Rust crate (mentioned in the article) it just happens that there's no Python bindings available for that.