On 5/3/23 01:46, Felipe Contreras wrote:
To be honest this whole approach seems to be completely flawed to me and
against the whole design of git in the first place.
The discussion above is mostly moot now since this has been fixed in
later patches in this thread, AFAIK. It's also moot for other reasons,
like the hash function transition plan is not really implemented, yet.
Also, this was about corner-case, like it often is.
In a recent email Linus Torvalds explained why object ids were
calculated based {type, size, data} [1], and he explained very clearly
that two objects with exactly the same data are not supposed to have the
same id if the type is different.
This is different. But aside, type + size + data are not really much
different from just having data in a hash function. There are plenty of
hash collisions where
HASH(type + size + data) == HASH(type + size + data')
by definition of how these functions work. The problem is always in
finding these collisions. But anyway...
In my view one repository should be able to have part SHA-1 history,
part SHA3-256 history, and part BLAKE2b history.
Yes, that would be great. Please provide patch series for this :-)
I have not been following the SHA-1 -> OID discussions, but I
distinctively recall Linus Torvalds mentioning that the choice of using
SHA-1 wasn't even for security purposes, it was to ensure integrity.
These are different sides of the same coin. Hashes are used to provide
integrity. Hashes like MD4, MD5, SHA1, SHA256 are there for integrity.
Some of these are no longer recommended and some are completely broken.
Better the SHA-1 you know, than the SHA-256 you don't.
Wrong conclusion ;) Also, we know SHA-256
The problem in git-core and virtually all clients and other
implementations is/was that SHA1 was hardcoded and assumed to be THE ONE
and ONLY hash. It will take quite a bit of work outside of git-core to
remove this one assumption (remember two digit year and 2000? - yes I'm
old). Once this hash assumption is removed, you can start talking about
adding other hashes and interop.
Keep in mind -- hashes are there for object reference. They are the glue
in git. But there is really nothing stopping us from recalculating them
"on the fly". If you have SHA1 repo, you can calculate a SHA256 or
whatever hash for any type object. That's not the problem, conceptually
speaking.
Finally, let not have a "bike shed" discussion about this. The
GIT_DEFAULT_HASH is meant to be used by `git init` in-lieu of
--object-format parameter, so it's not flawed. When used in other
applications, it probably indicates a bug. But we can't fix all the bugs
at once :-)
Cheers,
- Adam
