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

changes_comments should have compound foreign key (file_id, hash) #23

Closed
nanokatze opened this issue Feb 1, 2017 · 2 comments
Closed
Labels

Comments

@nanokatze
Copy link
Contributor

nanokatze commented Feb 1, 2017

There can exist same change hash for two or more different files. Example:

  1. you open two files with exactly same content
  2. their base changes are both 0
  3. erase first 4 bytes in both
  4. change hash is sha256(base + file_pos + change_type + data)
  5. get collision
@nanokatze nanokatze added the bug label Feb 1, 2017
@nyxxxie
Copy link
Owner

nyxxxie commented Feb 7, 2017

@fst3a is this fixed with sqlalchemy changes in feature/implement_project?

@nanokatze
Copy link
Contributor Author

@nyxxxie no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants