6 ms·
No IV, ECB mode... why bother with encryption at all? Just expose the internal id.
by fodkodrasz 3y ago
No IV, ECB mode... why bother with encryption at all? Just expose the internal id.
- remram 3y agoBecause the internal ID exposes timing/sequence information, as per jonhohle's comment.
- bajsejohannes 3y agoYou would still use a secret key, so it's impossible for the end user to decrypt it.
- adrian_b 3y agoEncrypting an internal id with ECB into an external id continues to allow the comparison for equality of 2 ids, to determine whether they are the same or not, but except for this it removes all the information contained in the structure of an UUID.
- computerfriend 3y agoECB is perfectly secure when you use it on a single block.
- fodkodrasz 3y agoAnd you have no problem with the same data being encrypted being identifyable (no salt). i see now why it might be useful in this case, though I still don’t like the idea, it feels bad somehow. (Yeah I get that you save storage for some computation)
- isbvhodnvemrwvn 3y agoYou are encrypting a single block of unique information. No other encryption mode gives you any advantages whatsoever.