3 ms·
I agree. That's why "keep the data on the server" is preferable to "send it to the user but protect it with custom crypto".
by NateLawson 17y ago
I agree. That's why "keep the data on the server" is preferable to "send it to the user but protect it with custom crypto".
- joe_the_user 17y agoYes, Having a narrative reinforces the point that what you actually do depends on the entire context of the application. You would almost never be the one implementing cannot-be-broken-under-ANY-circumstances encryption. So you have to know what the circumstances are. In this case, the circumstances point to no-encryption-whatsoever! Sure, you could point to other circumstances where something like what they're talking about would be useful but that's a million possible circumstances with a million possible encryption solutions and you've lost the useful urgency of the original concrete narrative.