3 ms·
Should we assume that all cell phones are compromised (or can be by nation states and cyber criminals whenever they like)? I believe we should. That assumption
by _wldu 5y ago
Should we assume that all cell phones are compromised (or can be by nation states and cyber criminals whenever they like)? I believe we should.
That assumption implies that they have access to private/secret keys on our phones.
How do you build software to be secure and private in that scenario?
- deleted 5y ago[deleted]
- supermatt 5y agoYou run it in an environment that you DO trust - i.e. a TEE (Trusted Execution Environment). This can be a separate device (physically attached or networked), integrated hardware (e.g. IME/SEP/etc), or some form of isolation built into the hardware (e.g. SGX/PSP/etc). But this has major limitations - especially if you are trying to communicate from an untrusted layer, as it can still be intercepted. Only what happens INSIDE the TEE is secure, and theres no guarantee you are even communicating with it. This is why they are generally only used for verification, secured RNG (including OTP), protected decryption of insensitive data (i.e. DRM), etc. Basically where you dont particularly care about the input or output (or both), just that the operation itself needs to be secure.