New fuzzing tool finds USB bugs in Linux, Windows, macOS, and FreeBSD

Re:New fuzzing tool finds USB bugs in Linux, Windows, macOS,... by MaxBarraclough on Thursday May 28, 2020 @08:44AM (#23336583)

So the machinist had been using rigorous testing, catching all defects prior to release, rather than using a correct-by-construction methodology. Either approach seems fine.

[ Parent | on HN ]

Re:New fuzzing tool finds USB bugs in Linux, Windows, macOS,... by bluGill on Thursday May 28, 2020 @10:09AM (#23337393)

Neither is perfect. Tests are only as good as your imagination of what to test. Proof by construction is only as good as your ability to have the right axioms

[ Parent | on HN ]

Re:New fuzzing tool finds USB bugs in Linux, Windows, macOS,... by MaxBarraclough on Thursday May 28, 2020 @01:17PM (#23339877)

> Tests are only as good as your imagination of what to test.

A lot of work has been done on code-coverage, boundary-analysis, etc. Testing can never be complete, though.

> Proof by construction is only as good as your ability to have the right axioms

That's not a good summary of the challenges that formal methods face with respect to correctness. Defects can creep in at various points.

See p. 46 of the PDF linked from https://www.adacore.com/tokeneer

[ Parent | on HN ]

Re:New fuzzing tool finds USB bugs in Linux, Windows, macOS,... by monadic2 on Thursday May 28, 2020 @04:31PM (#23342184)

Well, apparently it didn’t catch the defect that mattered. Typical engineer trying to justify an engineering mistake!

[ Parent | on HN ]

Re:New fuzzing tool finds USB bugs in Linux, Windows, macOS,... by hawski on Thursday May 28, 2020 @03:19PM (#23341248)

He never had problem with use-after-free, because he was leaking memory.

[ Parent | on HN ]