News for hackers. Stuff that matters.
Re:Multiple vulnerabilities released in NTP by lawnchair_larry on Friday December 19, 2014 @10:16PM (#8775765)
No, rewriting things in memory safe languages is absolutely something that should be done where it makes sense. There is no good reason to write things like ntpd in C anymore.

Anyone who says you'll just have a new set of similar issues is full of crap. You'll likely have issues, but ruling out memory corruption out the door is an indisputable win.

Re:Multiple vulnerabilities released in NTP by rian on Saturday December 20, 2014 @03:18AM (#8776136)
Well, there are still some good reasons to write things in C. For one it's standardized. Two it's ubiquitous.

I agree that projects should have a way to verify with 100% accuracy the memory safety of their code. One way to do that is to rewrite in another language.

Another way to do that is to use a static analyzer that lists out all unsafe operations in your codebase. Here's one http://goto.ucsd.edu/csolve/. Adds an extra build step / precommit-hook but IMO the cost/benefit is much better than rewriting your project. After all, we can't just rewrite our code every time a new safe language comes out.

Re:Multiple vulnerabilities released in NTP by lawnchair_larry on Monday December 22, 2014 @10:09AM (#8783292)
You don't seem to understand this problem space.
Re:Multiple vulnerabilities released in NTP by zzzcpan on Saturday December 20, 2014 @01:23AM (#8776008)
Ntpd should be replaced with something different, not rewritten. There is no reason to rewrite it. But I agree, there is no good reason to write such things in C anymore.