4 ms·
> you have to be able to also edit the size field in the header.” As I read the OP [1] a chosen-prefix collision attack such as this allows you to “edit the si
by bjornsing 7y ago
> you have to be able to also edit the size field in the header.”
As I read the OP [1] a chosen-prefix collision attack such as this allows you to “edit the size field in the header”. Or am I missing something?
1. “A chosen-prefix collision is a more constrained (and much more difficult to obtain) type of collision, where two message prefixes P and P’ are first given as challenge to the adversary, and his goal is then to compute two messages M and M’ such that H(P || M) = H(P’ || M’), where || denotes concatenation.”
EDIT: On second thought I was missing something: the adversary is further constrained in the git case because it must find M and M’ of correct length (specified in P and P’). Linus is right (as usual), this probably makes it much harder.
- bjornsing 7y agoA few emails forward in the thread Linus explains though why we don’t need to worry much about this attack in practice: https://marc.info/?l=git&m=148787287624049&w=2 https://marc.info/?l=git&m=148787287624049&w=2 This argument sounds sound to me.
- Thorrez 7y agoHis argument assumes the file is text and people read the entire thing. If either of those assumptions are false, then it's not safe. People store things in git that aren't text. Therefore it's not safe.