From: <rsbecker@nexbridge.com>
To: "'Hans Petter Selasky'" <hps@selasky.org>,
"'Konstantin Ryabitsev'" <konstantin@linuxfoundation.org>
Cc: <git@vger.kernel.org>
Subject: RE: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
Date: Fri, 13 Jan 2023 10:56:35 -0500 [thread overview]
Message-ID: <00b201d92767$a0403ee0$e0c0bca0$@nexbridge.com> (raw)
In-Reply-To: <6061d012-13b7-ca4b-5556-70875b65c887@selasky.org>
On January 13, 2023 10:50 AM, Hans Petter Selasky wrote:
>On 1/13/23 16:45, Konstantin Ryabitsev wrote:
>> I think you're misunderstanding some of the core principles of git.
>
>Maybe, I'm usually commandering git via the terminal.
>
>But if you say you can already edit stuff, why does the commit hash need to be
>cryptographic? I don't get that part. Yeah, I think of git commits like blockchain.
git is using SHA1/SHA256 (which happen to be coincidentally cryptographic) as message digests with a very low probability of collisions when the hashes are computed. There is never a situation, implied by cryptography, where there is a decode of a git hash. In order to make git a blockchain, you would need to implement central signing authorities, which would require a fork if the signature mechanism changes. The signature mechanism (SSH, GPG) is distinct from hash computation in git's trees, but depends on hash integrity.
next prev parent reply other threads:[~2023-01-13 16:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 12:59 Gitorious should use CRC128 / 256 / 512 instead of SHA-1 Hans Petter Selasky
2023-01-13 13:30 ` Konstantin Khomoutov
2023-01-13 13:39 ` Hans Petter Selasky
2023-01-13 14:21 ` rsbecker
2023-01-13 14:42 ` Hans Petter Selasky
2023-01-13 15:45 ` Konstantin Ryabitsev
2023-01-13 15:50 ` Hans Petter Selasky
2023-01-13 15:56 ` rsbecker [this message]
2023-01-13 16:02 ` Hans Petter Selasky
2023-01-13 15:54 ` Hans Petter Selasky
2023-01-13 16:02 ` Konstantin Ryabitsev
2023-01-13 16:06 ` Hans Petter Selasky
2023-01-13 16:18 ` Hans Petter Selasky
2023-01-13 16:36 ` Konstantin Ryabitsev
2023-01-13 16:44 ` Hans Petter Selasky
2023-01-13 16:49 ` Konstantin Ryabitsev
2023-01-13 16:51 ` Hans Petter Selasky
2023-01-13 16:27 ` Konstantin Ryabitsev
2023-01-13 16:30 ` Hans Petter Selasky
2023-01-13 16:35 ` Hans Petter Selasky
2023-01-13 16:41 ` Konstantin Ryabitsev
2023-01-13 16:45 ` Hans Petter Selasky
2023-01-13 15:15 ` Hans Petter Selasky
2023-01-13 17:44 ` Philip Oakley
2023-01-13 15:30 ` Konstantin Khomoutov
2023-01-13 15:39 ` Konstantin Ryabitsev
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 13:23 Hans Petter Selasky
2023-01-14 23:59 ` brian m. carlson
2023-01-15 3:14 ` Junio C Hamano
2023-01-15 10:09 ` demerphq
2023-01-16 7:21 ` Hans Petter Selasky
2023-01-16 7:23 ` Hans Petter Selasky
2023-01-16 12:34 ` rsbecker
2023-01-16 14:01 ` Hans Petter Selasky
2023-01-16 15:06 ` Junio C Hamano
2023-01-15 13:53 ` Michal Suchánek
2023-01-16 7:17 ` Hans Petter Selasky
2023-01-16 9:13 ` Michal Suchánek
2023-01-16 9:55 ` Hans Petter Selasky
2023-01-16 12:31 ` rsbecker
2023-01-16 14:10 ` Hans Petter Selasky
2023-01-16 19:08 ` Michal Suchánek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00b201d92767$a0403ee0$e0c0bca0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=hps@selasky.org \
--cc=konstantin@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.