Commit 1a9cd22a authored by damien clochard's avatar damien clochard 🐘

Merge branch...

Merge branch '182-anon-pseudo_email-not-generating-a-unique-email-for-each-different-salt-value' into 'master'

Resolve "anon.pseudo_email not generating a unique email for each different salt value"

Closes #182

See merge request !202
parents afd206c9 136adf13
Pipeline #237295814 passed with stages
in 4 minutes and 55 seconds
......@@ -217,6 +217,13 @@ SECURITY LABEL FOR anon
IS 'MASKED WITH FUNCTION anon.pseudo_email(users.login) ';
**NOTE** : You may want to produce unique values using a pseudonymization
function. For instance, if you want to mask an `email` column that is declared
as `UNIQUE`. In this case, you will need to intialize the extension with a fake
dataset that is **way bigger** than the numbers of rows of the table. Otherwise you
may see some "collisions" happening, i.e. two different original values producing
the same pseudo value.
**WARNING** : Pseudonymization is often confused with anonymization but in fact
they serve 2 different purposes. With pseudonymization, the real data can be
rebuild using the pseudo data, the masking rules and the seed. If an attacker
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment