Skip to main content
1 vote

What is a good strategy to avoid creating duplicate profiles for many individuals in a database?

Strategy 1 swaps one risk (leaking a private id) to another (leaking other private information, e.g. that a given person is a customer + request history). The attacker just needs to guess a customer ...
Christophe's user avatar
  • 82.3k
1 vote

What is a good strategy to avoid creating duplicate profiles for many individuals in a database?

Ok, I will try to make a shot in the dark - your question seems to miss some information, but let me see how far I can get from what you wrote. I think it is safe to assume customers are real persons, ...
Doc Brown's user avatar
  • 221k

Only top scored, non community-wiki answers of a minimum length are eligible