News for hackers. Stuff that matters.
Re:Libxml2's "no security embargoes" policy by codedokode on Thursday June 26, 2025 @04:39AM (#44385434)
The bug was about the case when malloc returns null, but the library doesn't check for it.
Re:Libxml2's "no security embargoes" policy by bjourne on Thursday June 26, 2025 @06:25AM (#44385961)
Correct, but the point is that it is difficult to get malloc to return null on Linux. Why litter your code with checks for de facto impossible scenarios?
Re:Libxml2's "no security embargoes" policy by daef on Thursday June 26, 2025 @07:50AM (#44386485)
in systems level programming (the introductory course before operating systems in our university) this was one of the first misconceptions to be eradicated. you cannot trust malloc to return null.
Re:Libxml2's "no security embargoes" policy by codedokode on Thursday June 26, 2025 @09:50AM (#44387412)
First, Linux has thousands of settings that could affect this, second the library probably works not only on Linux.