News for hackers. Stuff that matters.
Re:Lua support in the NetBSD kernel by vor_ on Wednesday October 16, 2013 @08:22PM (#6562922)
What concerns?
Re:Lua support in the NetBSD kernel by robert-wallis on Wednesday October 16, 2013 @09:32PM (#6563156)
sprintf buffer overflow in the string library https://github.com/LuaDist/lua/commit/52eff16f51750cf47afaa5...

This library is not included in NetBSD as far as I can tell: http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/modules/lua/?onl...

But it's an indication that it shouldn't be included in a Kernel.

Re:Lua support in the NetBSD kernel by Sanddancer on Thursday October 17, 2013 @04:13AM (#6564166)
There were buffer overflows in the Linux kernel in 2012 ( http://www.securityfocus.com/bid/53401 ). Should we not have filesystems in the kernel either?
Re:Lua support in the NetBSD kernel by robert-wallis on Thursday October 17, 2013 @01:08PM (#6566657)
Certainly the string library, of all places, should be using secure code.

I'm sure there are sooo many people running Linux on pre-OSX Mac harddrives formatted with HFS that could be hacked with a buffer overflow.

Are you seriously arguing that buffer overflows in the kernel are not a big deal?

Re:Lua support in the NetBSD kernel by pdpi on Thursday October 17, 2013 @06:59AM (#6564561)
Well... No, if you're a proponent of the micro-kernel design.
Re:Lua support in the NetBSD kernel by tedunangst on Wednesday October 16, 2013 @09:38PM (#6563181)
You linked to a 24,000 line diff to point out what exactly?
Re:Lua support in the NetBSD kernel by robert-wallis on Wednesday October 16, 2013 @09:43PM (#6563197)
wait for it... the exact section of the code that contains the "sprintf" I mentioned will pop into your screen. Just be patient.
Re:Lua support in the NetBSD kernel by scott_karana on Wednesday October 16, 2013 @09:05PM (#6563080)
GP was probably in response to ketralnis' comment. :)
Re:Lua support in the NetBSD kernel by ketralnis on Wednesday October 16, 2013 @09:48PM (#6563216)
recuter's comment already existed when I wrote mine, so it couldn't be in response to me