Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by mrtksn on Tuesday September 26, 2023 @10:13AM
(#37659645)
>None of those are suitable options for an image decoding library on the range of WebP supported platforms.
What makes these unusable for this task?
Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by sp332 on Tuesday September 26, 2023 @10:17AM
(#37659712)
They need a large runtime and are slow to start up.
Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by mrtksn on Tuesday September 26, 2023 @11:38AM
(#37660946)
Is that true for all memory safe languages? Why?
Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by marcosdumay on Tuesday September 26, 2023 @12:29PM
(#37661734)
> Is that true for all memory safe languages?
No. That is true for the list upthread (well, if you consider runtimes measuring a couple of MB "large", it's reasonable but quite arguable). It doesn't have much correlation with any feature.
Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by pjmlp on Tuesday September 26, 2023 @11:31AM
(#37660840)
Modula-2, Ada, Object Pascal, D would be.
What makes them unsuitabe is lack of widespread compiler support across those platforms, if we ignore how long Ada has been available in GCC.
And Modula-2 is now in GCC as well.
Re:Google assigns a CVE for libwebp and gives it a 10.0 score
by assassinator42 on Tuesday September 26, 2023 @12:46PM
(#37662036)
Ada has the bounds checking, but doesn't (AFAIK) have a safe way to deallocate dynamic memory. At least as of now, there is a proposal to add something like Rust in the future.
It also has memory unsafe concepts like specifying an address for a variable.
None of those are suitable options for an image decoding library on the range of WebP supported platforms.