News for hackers. Stuff that matters.
Re:Memory Safety for Web Fonts by kiicia on Wednesday March 19, 2025 @12:29PM (#43414147)
The real issue is the effort required to rewrite everything without introducing new bugs resulting from a misunderstanding of the original code
Re:Memory Safety for Web Fonts by kevingadd on Wednesday March 19, 2025 @12:34PM (#43414234)
New (likely aesthetic only) bugs in font rendering are probably considered preferable to existing security vulnerabilities, I would hope.
Re:Memory Safety for Web Fonts by kiicia on Wednesday March 19, 2025 @03:32PM (#43416366)
it's hard to argue that "occasional accent rendering issue" is better than "occasional zero-click issue", but rewriting code of any actual complexity is hard in practice... and we are talking about only one library here, with thousands libraries and utils to go
Re:Memory Safety for Web Fonts by arccy on Wednesday March 19, 2025 @12:48PM (#43414389)
if you have too many aesthetic bugs, nobody will use it. it then becomes the most secure code because it doesn't run anywhere so can't be exploited.
Re:Memory Safety for Web Fonts by kortilla on Wednesday March 19, 2025 @01:30PM (#43414924)
“Aesthetic only” bugs for a project entirely for aesthetics can easily kill the usage of it.

Nobody cares about a CVE-free rendering library if it can’t render things correctly.

Re:Memory Safety for Web Fonts by adgjlsfhk1 on Wednesday March 19, 2025 @03:46PM (#43416498)
that really depends. There are thousands of languages in the world in dozens of alphabets and I currently only have a hope of reading text in a latin alphabet. As such, even a rendering library that misrendered 99% of unicode but was CVE free would be a major win for me (and hundreds of millions of people)