3 ms·
So add a new object to the git repo (open source projects usually allow contributions) for which you already have a malicious SHA1-colliding object in your pock
by andrewflnr 10y ago
So add a new object to the git repo (open source projects usually allow contributions) for which you already have a malicious SHA1-colliding object in your pocket. If your change is widely distributed, you now have a hash in the wild that matches your malicious data.
- hueving 10y agoRight, assuming it goes through no revisions for code review and doesn't get rebased, that could potentially work. You would need to figure out where to have some random data in the commit that you're altering to search for the collision. Maybe some "test data" or something and hope nobody asks you to remove it.