From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Ulrich Drepper via Gcc <gcc@gcc.gnu.org>
Subject: Re: commit signing
Date: Wed, 14 Sep 2022 14:07:14 +0200 [thread overview]
Message-ID: <YyHD8kwFVGJomghD@tucnak> (raw)
In-Reply-To: <CAFiYyc1r0JKh1VG_=YSuvzp2QWs+wsU_C6=4O79iwABOSxDx8Q@mail.gmail.com>
On Wed, Sep 14, 2022 at 01:31:06PM +0200, Richard Biener via Gcc wrote:
> How does this improve supply chain security if the signing happens
> automagically rather than manually at points somebody actually
> did extra verification? That is, what's the attack vector this helps with?
>
> What's the extra space requirement if every commit is signed? I suspect
> the signatures themselves do not compress well.
Note, right now we sign the release tags and I think one basepoint
(basepoints/gcc-11) is signed too (but the rest of them aren't).
Jakub
next prev parent reply other threads:[~2022-09-14 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 9:11 Ulrich Drepper
2022-09-14 9:15 ` Jonathan Wakely
2022-09-14 11:31 ` Richard Biener
2022-09-14 12:07 ` Jakub Jelinek [this message]
2022-09-14 12:07 ` Ulrich Drepper
2022-09-28 17:03 ` Ulrich Drepper
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=YyHD8kwFVGJomghD@tucnak \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).