I'm a bit uneasy about this. Since checksumming is not collision-resistant, I would be careful just relying on this. The goal was to avoid diffing files but I don't know what is the fastest way.
In any case, I guess a checksum is not enough to guarantee file integrity (against malice). Maybe adding file size would do. On Wednesday, August 3, 2016 at 7:36:36 PM UTC+2, Daniel Theophanes wrote: > > What is the purpose of this? For instance, In govendor the hash of the > files, file names, and path is computed and recorded. That way if they are > modified it is detected. So yeah, md5 or blake2 would work just fine. > > On Wednesday, August 3, 2016 at 10:14:53 AM UTC-7, atd...@gmail.com wrote: >> >> Would a md5 hash suffice? >> >> I mean, it is probably easy to create collisions, but the source still >> needs to compile so... >> >> Or an md5 hash and using go/types to make sure that any object escaping >> the package boundaries is still present and none other have been added. >> >> Any idea? >> >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
