3 ms·
I'm not an expert, but here's some conserns I'd have: Because the returned payload isn't necessarily uniform. Because you aren't guaranteed uniqueness (or that
by kebman 6y ago
I'm not an expert, but here's some conserns I'd have:
Because the returned payload isn't necessarily uniform. Because you aren't guaranteed uniqueness (or that guarantee is mathematically lower). And because the overhead for doing it that way may be too high (we want to achieve it in a way that is computationally light, and most encryption isn't).
- antoinealb 6y agoI am not sure what your concern ab ou it uniqueness is: encrypti on has to be invertible, therefore if each non encrypted integer is unique, it means that each encrypted representation is also unique. w.r.t encryption cost, I think AES is very cheap on modern hardware compared to the cost of SQL or the overhead of writing your app in an interpreted language.
- holtalanm 6y ago> Because you aren't guaranteed uniqueness If your encrypted value is not unique, then your encryption algorithm is broken. You have to be able to turn the encrypted value back into the unencrypted value. if you have two unique unencrypted values that result in the same encrypted value, then that essentially makes it impossible to unencrypt.
- layoutIfNeeded 6y ago>Because the returned payload isn't necessarily uniform Wrong. Flipping a single plaintext bit flips all ciphertext bits with 50% probability. >Because you aren't guaranteed uniqueness Wrong. Encryption is bijective. >And because the overhead for doing it that way may be too high Wrong. Symmetric ciphers are extremely fast.