2 ms·
You mean, when you look at your code, or someone else does, they think it's ok? I guess that's why security issues, even in massively peer reviewed code, are a
by b112 5y ago
You mean, when you look at your code, or someone else does, they think it's ok?
I guess that's why security issues, even in massively peer reviewed code, are a thing of the past, right?
Do your best, code as safely and securely as you know how, peer review and test and fuzz...
Then when you deploy your code, treat it as vulnerable, because history days it likely is.
Treat your phone as compromised. Anything network connected as compromised.
Because history says it can be, and easily.
Monitoring is one of the most important security measures for a reason.
- CorrectHorseBat 5y agoThere does actually exist such a thing as formally proven code, which is mathematically according to spec. https://www.sel4.systems/Info/FAQ/proof.pml https://www.sel4.systems/Info/FAQ/proof.pml
- b112 5y agoI don't even see the point you are making. Are you trying to claim that the above proof will never be invaldated? You're really just proving mt point here. You think thongs can be secure.
- kobebrookskC3 5y agowhat do you mean invalidated? the point of proofs is that they will be still be as true today as they will millenia into the future. pythagoras' theorem is just as true today as it was millenia ago.
- CorrectHorseBat 5y agoYes, that's what I'm claiming. That's of course only a part of the story, the spec or the hardware can still be broken.