I hope that we can finally discuss image formats without it getting torpedo’d with “jxl is the format Google doesn’t want you to use”
I’m also curious if the decoder being in Rust pays off into tangibly less surface considering how devastating the libwebp and libvpx memory exploits were, I suppose only time will tell
Also consider that libjxl 0.12, which was released in july, contained several security fixes (to the degree that there’s a suggestion to upgrade at the top of their README).
I think this validates Google’s and Mozilla’s decision to hold off until there’s a viable Rust alternative (whether that was an explicitly stated reason, as in Mozilla’s case, or just happenstance).
Extensive security and hardening fixes across the core decoder/encoder, box
buffers, and plugins (EXR, GIF, APNG/PNG, PAM/PNM/PGX). This includes fixes
for integer overflows/underflows, out-of-bounds reads/writes, buffer
overflows, and null pointer guards
\o/
I hope that we can finally discuss image formats without it getting torpedo’d with “jxl is the format Google doesn’t want you to use”
I’m also curious if the decoder being in Rust pays off into tangibly less surface considering how devastating the libwebp and libvpx memory exploits were, I suppose only time will tell
score 1 · canonical
Certainly can’t be worse :)
score 1 · canonical
Also consider that libjxl 0.12, which was released in july, contained several security fixes (to the degree that there’s a suggestion to upgrade at the top of their README).
I think this validates Google’s and Mozilla’s decision to hold off until there’s a viable Rust alternative (whether that was an explicitly stated reason, as in Mozilla’s case, or just happenstance).
score 5 · canonical
Oh damn I didn’t know about that, for sure then.
score 1 · canonical