Duy Nguyen wrote: > The biggest obstacle is the assumption of SHA-1 everywhere in the > source code (e.g. assume the object name always takes 20 bytes). Brian > started on cleaning that up [1] but I think it's stalled. Then we need > to deal with upgrade path for SHA-1 repos. I think the biggest obstacle is the upgrade path. ;-) If the upgrade path is taken care of, I won't mind writing and reviewing a coccinelle-generated patch to replace 20, 40, 21, 41, and so on with appropriate constants. Or we can take the first 20 bytes of a SHA-256, which is already supposed to have better security properties than SHA-1. Another obstacle is hard-coded SHA-1s in tests. Thanks, Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html