Timeline for User identity anonymization
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2018 at 7:07 | history | tweeted | twitter.com/StackSecurity/status/951349804147314688 | ||
| Jan 8, 2018 at 19:54 | comment | added | kmaork | But if you concatenate the user name with an incrementing number, the filenames will be different and brute-force won't work because of the secret key | |
| Jan 8, 2018 at 13:40 | comment | added | nrofis | @Ni. it is the same idea as my first solution because the original file name is the user ID | |
| Jan 7, 2018 at 17:25 | comment | added | kmaork | How about saving the filenames as md5(secret_key+original_filename)? | |
| Jan 7, 2018 at 16:24 | vote | accept | nrofis | ||
| Jan 7, 2018 at 16:16 | answer | added | LSerni | timeline score: 2 | |
| Jan 7, 2018 at 15:32 | history | edited | nrofis | CC BY-SA 3.0 |
added 269 characters in body
|
| Jan 7, 2018 at 15:27 | comment | added | nrofis | @Ni. True, exactly what you said and without other people seeing even one file name being able to identify the user that owns it | |
| Jan 7, 2018 at 15:09 | comment | added | kmaork | Can you explain the problem in a more generic way? Do you need to be able to find the files using a user id, without other people seeing the file names being able to identify they are from the same user? | |
| Jan 7, 2018 at 12:34 | history | edited | nrofis | CC BY-SA 3.0 |
added 56 characters in body
|
| Jan 7, 2018 at 12:00 | review | First posts | |||
| Jan 7, 2018 at 17:22 | |||||
| Jan 7, 2018 at 11:53 | history | asked | nrofis | CC BY-SA 3.0 |