Re: Gitorious should use CRC128 / 256 / 512 instead of SHA-1

From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Date: Jan 13, 2023, 15:39 UTC
Message-ID: <20230113153932.gsnt4t26tlzotw65@meerkat.local>
In-Reply-To: <446984f6-0d2e-04da-11a3-8b1481fac953@selasky.org>

On Fri, Jan 13, 2023 at 02:39:37PM +0100, Hans Petter Selasky wrote:

> Just imagine the consequences of finding child porn inside a 10-year old
> firmware binary blob in the Linux kernel. Will you just ignore it, or will
> you fix it?

How do you expect something like this would happen? A much more likely scenario would be someone contributing a binary blob that doesn't actually allow redistribution, and therefore would need to be purged from the repository.

When something like this happens, everyone is given a heads-up, the history is rewritten, and everyone moves on. It's a fairly routine procedure -- ask anyone who's ever committed an API key into their repo.

Git supports history edits and everyone lives with it just fine -- I think you are under the impression that git is some kind of globally distributed blockchain where any history edit requires a consensus fork. It's not at all the case.

-K