I am developing a webapp that does not reveal record count, because it hides the primary key. I am looking for a better way to do this. My favorite idea is to encrypt the ID itself with a block ...
If I encrypt some data with a randomly generated Key and Initialization Vector, then store all three pieces of information in the same table row; is it necessary to encrypt the IV as well as the Key? ...
Edit: I'll put up this more clearly. By the most simplest form, I'm asking that if I AES encrypt in CTR more with Mcrypt (using PHP), can I create the "IV" by just simply reading 16 bytes from ...