Buffer overflow when pwfeedback is set in sudoers

Re:Buffer overflow when pwfeedback is set in sudoers by jaas on Sunday February 02, 2020 @02:07PM (#22218672)

This is a naive and dangerous perspective. You're basically saying that memory safe languages don't solve all problems so it's fine to use unsafe languages.

Don't write code in unsafe languages unless you have to (almost never for new code). Period. You will have some problems either way, but you will have fewer problems in a memory safe language.

Pen testing is not even remotely a good mitigation to depend on against the dangers of a language like C. Its fine to do for defense in depth and to find problems not related to memory safety, but it's no substitute for making a more sensible language choice.

[ Parent | on HN ]

Re:Buffer overflow when pwfeedback is set in sudoers by pjmlp on Sunday February 02, 2020 @06:37PM (#22220240)

That is the classical defense from C camp, going back to the 80's Morris worm.

[ Parent | on HN ]

Re:Buffer overflow when pwfeedback is set in sudoers by loeg on Sunday February 02, 2020 @02:54PM (#22218992)

Sudo isn't new code in any sense. "Rewrite the world in memory safe languages" is appealing if you completely discount the time and cost required to do so.

[ Parent | on HN ]

Re:Buffer overflow when pwfeedback is set in sudoers by desc on Sunday February 02, 2020 @05:52PM (#22220034)

And all the new bugs introduced in the process.

[ Parent | on HN ]

Re:Buffer overflow when pwfeedback is set in sudoers by jaas on Sunday February 02, 2020 @03:57PM (#22219364)

I didn't say that.

[ Parent | on HN ]