When our closed systems misbehave, my only option is to shrug and ask if we have a support contract.
ie, Given enough code, all reviews are shallow?
It's more just that you have lots of groups exercising the code and looking into various portions of the code - if every group decides "Yep, the portion we use/looked at is solid", then you gain some confidence that the code does what it's supposed to. The more groups using/perusing the code, the more confidence you gain.
there's nothing magic about switching your machine off to increase security. It's just as vulnerable when you're using it, more so in fact. I'm not sure how shutting your machine off adds any predictability either. If you want to achieve the same thing just turn off wifi.
For mac laptop users we get the best of both worlds, always state preserving, but essentially "off" when not in use. Sadly neither windows nor linux have ever got "sleep" right.
Another good point spolu brings up:
This detail doesn't get a lot of discussion, but I think it's sometimes an essential fallacy of the very premise of the open source concept, that having the ability to audit source code, doesn't necessarily make it a realistic option.Lots of modern contraptions are simply too complex for any individual to ever claim a hope of gaining an honest understanding of their inner workings, nevermind an unskilled layman. At least, not without living like a cleric, cloistered away in the library of some convent or monastery for most of one's life. Sometimes I feel that the real hazard is that we gloss over the idea that we're trying to exert control over a massive arrangement of billions of transistors, however small they may be. If we were confronted with an elaborate array of ordinary light switches, and told to conquer the same tasks, I think it'd be easier to realize the true scale of some of the things we fiddle with on an everyday basis.