4 ms·
Slower != secure. But secure implies slower. Therefore, fast as possible implies not secure.
by NegativeK 3y ago
Slower != secure.
But secure implies slower. Therefore, fast as possible implies not secure.
- slowmovintarget 3y agoSo theater. You actually do need to present consistently slow evaluation times when handling encrypted values, as failing fast gives out information that can be used for cracking. But other than that, there usually isn't a good reason to do it.
- NegativeK 3y agoThe article specifically mentions why fully unsupervised, no "friction" processes lead to actual, specific problems. You could slow your stuff down without securing it in response to the article's idea, but that's not what I was referring to in my comment.