Re:Notepad++ drops code signing for its releases
by 0815test on Thursday March 07, 2019 @01:10PM
(#19330450)
If your compiler correctly enforces security properties (and many languages do attempt to do this, at least in well-defined "safe" subsets), then of course any source code compiled with it is going to be safe. It's the difference between the JavaScript/WASM JIT-powered sandbox on the one hand, and the ActiveX code-signing-based model on the other. Which is safer?
[ Parent
| on HN ]
Re:Notepad++ drops code signing for its releases
by CamperBob2 on Thursday March 07, 2019 @01:59PM
(#19331001)
What? A compiler can't tell if a given program is "safe" any more than it can tell if the program will halt.
Re:Notepad++ drops code signing for its releases
by 0815test on Thursday March 07, 2019 @02:14PM
(#19331153)
A compiler can tell if some program will halt, for many reasonable cases. For example, if the program comes with a proof that places it in some well-defined computational complexity class, a compiler will be able to tell that it halts. And even if a program cannot be said to halt in general, it can still be said to halt conditional on some "unsafe" assertions being true. Similarly, we can verify safety properties for many useful programs, and we can even use "unsafe" assertions to limit the extent of uncertainty about these properties that we cannot directly verify.
Re:Notepad++ drops code signing for its releases
by oarsinsync on Thursday March 07, 2019 @01:28PM
(#19330644)
I can visit a website and my CPU can get hammered to mine cryptocurrency for someone else without my consent.
I'm not sure either is that much better at this point!