#git bot interface

History of !sha1

• git uses a variant of the SHA1 cryptographic hash algorithm to ensure object integrity. Git v2.13.0 added hardening to the SHA-1 implementation to mitigate SHAttered; work towards a NewHash is underway: https://git.io/vpIMJ | Please note that purposeful SHA1 collisions are computationally expensive, and accidental encounters are more likely with wolves. https://en.wikipedia.org/wiki/Wolf_attacks Fear their howl!
  By Eugene at 2020-01-30 21:27:27
• git uses a variant of the SHA1 cryptographic hash algorithm to ensure object integrity. Git v2.13.0 added hardening to the SHA-1 implementation to mitigate SHAttered; work towards a NewHash is underway: https://git.io/vpIMJ | Please note that purposeful SHA1 collisions are computationally expensive, and accidental encounters are more likely with wolves. https://en.wikipedia.org/wiki/Wolf_attacks_on_humans Fear their howl.
  By Eugene at 2018-04-18 20:16:25
• Git's usage of SHA1 hashes is resistant to most attack vectors. Git v2.13.0 added hardening to the SHA-1 implementation to mitigate SHAttered; work towards a NewHash is underway: https://github.com/git/git/blob/master/Documentation/technical/hash-function-transition.txt | Please note that constructing an actual SHA1 collision is still computationally expensive, and accidental encounters are less likely than wolf attacks. Fear their
  By Eugene at 2018-04-18 20:09:04
• Git's usage of SHA1 hashes is resistant to most attack vectors. Additional mitigations and an eventual migration to other hash algorithms are planned. https://plus.google.com/+LinusTorvalds/posts/7tp2gYWQugL. Constructing an actual SHA1 collision is still very expensive, and accidental encounters are less likely than random wolf attacks. Fear their howl.
  By Eugene at 2017-02-25 21:43:09
• Git's usage of SHA1 hashes is largely immune to collisions because it includes a file-length header. Other protections and an eventual update to a new hashing algorithm are planned. https://plus.google.com/+LinusTorvalds/posts/7tp2gYWQugL. Constructing an actual SHA1 collision is still very expensive, and accidental encounters are less likely than random wolf attacks. Fear their howl.
  By Eugene at 2017-02-25 21:19:35
• Git's usage of SHA1 hashes is largely immune to collisions because it includes a file-length header. Other protections and an eventual update to a new hashing algorithm are planned. http://marc.info/?l=git&m=148787047422954. Constructing an actual SHA1 collision is still very expensive, and accidental encounters are less likely than random wolf attacks. Fear their howl.
  By Eugene at 2017-02-24 06:19:43
• Git's usage of SHA1 hashes is largely immune to collisions because it includes a file-length header. Other protections and an eventual update to a new hashing algorithm are planned. http://marc.info/?l=git&m=148787047422954
  By Eugene at 2017-02-24 06:17:49
• You shouldn't worry about collisions of object hashes as an attack vector against git. There is a higher probability that every member of your programming team will be eaten by wolves in unrelated incidents on the same night than a meaningful malicious collision will be constructed without the aid of the NSA.
  By eugenekay at 2012-07-16 15:43:34
• You shouldn't worry about collisions of object hashes as an attack vector against git. There is a higher probability that every member of your programming team will be eaten by wolves in unrelated incidents on the same night than a meaningful malicious collision is being constructed without the aid of the NSA.
  By EugeneKay at 2012-07-16 15:41:45