News for hackers. Stuff that matters.
Re:Hacking the Apple Webcam (Again) by wyager on Tuesday January 25, 2022 @07:14PM (#30080025)
The frustrating thing is that we know how to write absolutely secure browsers (or other executors/renderers/etc. of untrusted data) using formal methods. Unfortunately, because most of the negative externality falls on users who don't know any better, the economics don't really work out.
Re:Hacking the Apple Webcam (Again) by astrange on Tuesday January 25, 2022 @09:07PM (#30080776)
I'm not sure you can actually prove a TLS implementation is correct. It depends on the system clock being right, OCSP server being online, etc.

Even the encryption has to be free of side channels like timing attacks which are left out of what most people think of as a proof.

Re:Hacking the Apple Webcam (Again) by wyager on Wednesday January 26, 2022 @03:14PM (#30091070)
You can prove a TLS implementation correct up to defined assumptions (e.g. clock consistency). There are already some projects working on this, eg https://project-everest.github.io/
Re:Hacking the Apple Webcam (Again) by twox2 on Wednesday January 26, 2022 @11:31AM (#30087604)
Unlikely... these bugs are all logic bugs. They won't be mitigated by using formal methods, because most of these bugs adhere to pre-defined specs. The problem with browses is that these specs are often in conflict with each other for new and/or obscure features.
Re:Hacking the Apple Webcam (Again) by wyager on Wednesday January 26, 2022 @03:12PM (#30091035)
Logic bugs are the primary category of bugs targeted by heavyweight formal methods.

Most JS features don't even have a formal spec which is part of the problem.