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

Subject: Re: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
From: Hans Petter Selasky <hps@xxxxxxxxxxx>
Date: Mon, 16 Jan 2023 10:55:34 +0100
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <20230116091346.GC16547@kitsune.suse.cz>
References: <9c0fda42-67ab-f406-489b-38a2d9bbcfc2@selasky.org> <20230115135245.GB16547@kitsune.suse.cz> <b1984123-569a-c290-8048-158c1c5e08b4@selasky.org> <20230116091346.GC16547@kitsune.suse.cz>
User-agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1

On 1/16/23 10:13, Michal Suchánek wrote:

when that data is copied to a new location a new
CRC is calculated that can detect an error in that location.

Yes, that is correct, but what is "copying data"? Are you saying thatcopying data is always error free?


--HPS

Follow-Ups:
- Re: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
  - From: Michal Suchánek
- RE: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
  - From: rsbecker

References:
- Gitorious should use CRC128 / 256 / 512 instead of SHA-1
  - From: Hans Petter Selasky
- Re: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
  - From: Michal Suchánek
- Re: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
  - From: Hans Petter Selasky
- Re: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
  - From: Michal Suchánek