News for hackers. Stuff that matters.

A comment on OS X 10.11 buffer overflow with deep filesystem hierarchy. Parent comment

Re:OS X 10.11 buffer overflow with deep filesystem hierarchy by daenney on Saturday October 24, 2015 @07:29AM (#10443251)
That's because, license wise, they can't include GPL 3 licensed code, aka the GNU user space.

Also, this bug does not prove that the whole user space is completely broken. Many people use it daily without ever hitting these bugs. If you go looking for issues, you'll find them, just as you'll find them on Linux but in different places. Not to say this doesn't suck and we shouldn't fix them, but it's hardly proof of anything.

[ Parent | on HN ]
Re:OS X 10.11 buffer overflow with deep filesystem hierarchy by devit on Saturday October 24, 2015 @08:05AM (#10443347)
Where "can't" means "they don't want to because they want to reserve themselves the ability to screw their users by shipping devices with OSX or derivatives installed where the user cannot change the software, which the GPLv3 is specifically designed to prevent".

Considering handling paths is one of the most fundamental functions of the Unix tools and C library, having buffer overflows there is quite damning.

[ Parent | on HN ]
Re:OS X 10.11 buffer overflow with deep filesystem hierarchy by daenney on Saturday October 24, 2015 @10:17AM (#10443665)
Regardless of your personal dislike of the vendor, there have been plenty of buffer overflows and other bugs in coreutils/fileutils. The Mac/BSD user space is by no means an exception.
[ Parent | on HN ]
Re:OS X 10.11 buffer overflow with deep filesystem hierarchy by lmm on Saturday October 24, 2015 @02:56PM (#10444503)
Which is a real indictment of C, when programs this simple have bugs this severe.
[ Parent | on HN ]