From: Junio C Hamano <gitster@pobox.com>
To: Hans Petter Selasky <hps@selasky.org>
Cc: rsbecker@nexbridge.com,
"'brian m. carlson'" <sandals@crustytoothpaste.net>,
git@vger.kernel.org
Subject: Re: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
Date: Mon, 16 Jan 2023 07:06:09 -0800 [thread overview]
Message-ID: <xmqqbkmyecym.fsf@gitster.g> (raw)
In-Reply-To: <85788356-14b1-6afb-c78c-0ab889bbbb59@selasky.org> (Hans Petter Selasky's message of "Mon, 16 Jan 2023 15:01:07 +0100")
Hans Petter Selasky <hps@selasky.org> writes:
> From what I've read the GPLv3 goes pretty far to also provide flashing
> rights for software, but what use is that, when flashing the unsigned
> software on your Samsung phone, for example, some fuse breaks in the
> hardware, and then you can no longer use certain apps on your phone?
It smells that you are conflating the signing of source material and
the sealing of tivoized hardware that use cryptographic signature to
tell what binaries are allowed to run on it.
The signing implemented by the software we the Git development
community build is not about the latter. The source used to build
binaries for your tivoized hardware can come from a VCS that is
deliberately designed to allow object name collisions, and your
build would just be locked out the same unless you have the signing
key that pleases the hardware. Use of Git there would not make the
story any different, I am afraid.
next prev parent reply other threads:[~2023-01-16 15:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 13:23 Gitorious should use CRC128 / 256 / 512 instead of SHA-1 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 12:59 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
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
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=xmqqbkmyecym.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hps@selasky.org \
--cc=rsbecker@nexbridge.com \
--cc=sandals@crustytoothpaste.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox