How To Prevent the Next Heartbleed - Slashdot

Become a fan of Slashdot on Facebook

×

How To Prevent the Next Heartbleed 231

Posted by timothy on Saturday May 03, 2014 @10:05PM from the leave-your-comment-in-the-form-of-an-exploit dept.

dwheeler (321049) writes "Heartbleed was bad vulnerability in OpenSSL. My article How to Prevent the next Heartbleed explains why so many tools missed it... and what could be done to prevent the next one. Are there other ways to detect these vulnerabilities ahead-of-time? What did I miss?"

This discussion has been archived. No new comments can be posted.

How To Prevent the Next Heartbleed

Search 231 Comments Log In/Create an Account

Comments Filter:

Re:In the US: force the NSA to disclose them (Score:0, Funny)

by Anonymous Coward writes: on Saturday May 03, 2014 @11:52PM (#46911283)

Exactly. The Republicans that create these bugs will never allow them to be disclosed by the government. There's a reason Republicans still push so hard for C and only C to be used for projects.

Parent Share
twitter facebook
Re:How about (Score:5, Funny)

by Kazoo the Clown ( 644526 ) writes: on Sunday May 04, 2014 @12:01AM (#46911307)

Yes, I think it's clear the next gen of CPUs really needs to have the machine language removed entirely. What a security hole!

Parent Share
twitter facebook

There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.

Related Links Top of the: day, week, month.

390 comments32-Hour Workweek for America Proposed by Senator Bernie Sanders
358 commentsWhat Should Happen to Empty Downtown Office Spaces?
340 commentsHacktivism Erupts In Response To Hamas-Israel War
324 comments'Feedback' Is Now Too Harsh. The New Word is 'Feedforward'
248 commentsWorkers are Resisting Calls to Return to Offices

There are two ways to write error-free programs; only the third one works.