Hacker GitHub

← All repos

bradfitz/gitbrute

View on GitHub ↗ ★ 397 Go

brute-force a git commit hash

7 mentions on Hacker News by 7 people: 1 story, 6 comments · first 2014-04-06 · latest 2021-09-02

Mentions per year 7 mentions · busiest year 2014 (3)
20082026
AllStoriesComments NewestTopOldest
  1. …asking, but it is trivially easy to fake a git short hash to whatever you like. I cloned this repo: https://github.com/bradfitz/gitbrute Ran the command in the readme (had to do it twice for some reason) and the latest commit is now 000001…
    comment by Genbox · 2021-09-02 · in Improving Git protocol security on GitHub
  2. …pretty much no time. Prefixes are always going to be insecure because they are so short. In fact, https://github.com/bradfitz/gitbrute exists.
    comment by GlitchMr · 2020-02-04 · in A new hash algorithm for Git
  3. …fudged by 90 minutes without detection, you might not need any dummy comments or files at all. [1] https://github.com/bradfitz/gitbrute
    comment by michaelt · 2017-02-23 · in Announcing the first SHA-1 collision
  4. …hash. It took someone 30 mins to brute first 8 hex letters (of 40) on a MBP [1] with that. [0] https://github.com/bradfitz/gitbrute [1] https://github.com/bradfitz/deadbeef/commit/deadbeefa1a98280...
    comment by shurcooL · 2016-02-07 · in Git-blame-someone-else – Blame someone else for your bad code
  5. …this commit, I'm guessing gitbrute uses miniscule variations in the commit time instead. EDIT: yep: https://github.com/bradfitz/gitbrute/blob/master/gitbrute.go
    comment by spb · 2014-04-07 · in Note the commit hash
  6. …that (as the name suggests) brute-forces the prefix of the hash to whatever you like. [1]: https://github.com/bradfitz/gitbrute
    comment by poopicus · 2014-04-06 · in Note the commit hash