Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement k-anonymity #44

Closed
csirianni opened this issue Dec 11, 2023 · 0 comments · Fixed by #45
Closed

Implement k-anonymity #44

csirianni opened this issue Dec 11, 2023 · 0 comments · Fixed by #45
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@csirianni
Copy link
Owner

Divide passwords into tables corresponding to the leaked byte(s). That is, each table will be named after the integer value of the leaked byte(s). If we leak only one byte, then the names of tables range from [0, 255].

Limit the # of leaked bytes to 4 (or 3, up to you).

This will change our db initialization inmain.cpp and some unit tests, but don't change the Database class. Try to change as few tests as possible. We still need the key table, but we don't need to passwords table.

@csirianni csirianni added the enhancement New feature or request label Dec 11, 2023
@csirianni csirianni added this to the Sprint 3 milestone Dec 11, 2023
@csirianni csirianni moved this to In Progress in PDL Kanban Dec 11, 2023
@stellaljung stellaljung linked a pull request Dec 11, 2023 that will close this issue
@github-project-automation github-project-automation bot moved this from In Progress to Done in PDL Kanban Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants