But secure implies slower. Therefore, fast as possible implies not secure.
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.
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.
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.