Skip to main content
8 events
when toggle format what by license comment
Sep 3, 2024 at 20:56 comment added Moshe Katz Reflections on Trusting Trust (PDF), by Ken Thompson, is every bit as relevant today as it was when he wrote it in 1984.
Aug 31, 2024 at 2:39 comment added mbrig @PeterGreen and unless you are building your own hardware out of discrete components, you need to fear the possibility of hardware backdoors.
Aug 31, 2024 at 1:23 comment added Peter Green There is a project called "live-bootstrap" to start from a tiny binary stub, small enough to hand audit and build up from there using only source code, which could in principle be audited. It's a long road though from the tiny binary stub to a modern OS and just because something can be audited doesn't mean it actually has been.
Aug 30, 2024 at 2:13 comment added chux "you may need to follow these steps for these pieces of software too" --> this leads to a viscous cycle - how to trust the compiler used to compile the compiler? A solution to break this cycle can be applied to the original issue and negate the need to download & compile.
Aug 29, 2024 at 19:10 comment added Kevin Chrome does indeed do this, but openly and behind an opt-in. Of course, it is not intended to nefariously steal the user's passwords, merely to help the user remember them. But it meets all of the technical criteria described in the question.
Aug 29, 2024 at 18:37 comment added wonderbear @schroeder I do not dispute this; it is however the theoretically correct solution to not trusting software.
Aug 29, 2024 at 16:13 comment added schroeder "reviewing the code yourself" takes an incredible amount of both time and skill for a browser. Once you include the OS ... forget about it. This answer is of limited usefulness...
Aug 29, 2024 at 15:10 history answered wonderbear CC BY-SA 4.0