Reply to thread

Message: [QUOTE="Arne Vajhøj, post: 5050669"] That relies on the key being kept secret. In many cases this is a necessary requirement, but not in this case, so I would say that it is second best option. And since Java UUID do provide a way to generate using a cryptographic secure RNG as markspace pointed out, then it it is even simpler to code than I expected (not that SecureRandom is that hard to use in the first place). If you make the column unique in the database then you will get an error inserting and can then just pick another. It will happen at average 1 out of some billion/trillion years, so I think you can live with that. You can sure pad and encrypt. But as explained above then I think it is just the second best option. Arne [/QUOTE]