public inbox for
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <>
Subject: [Bug Infrastructure/29615] prototype & document SOP for signed-git-op repo
Date: Thu, 01 Jun 2023 19:54:16 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #7 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #6)
> (In reply to Serhei Makarov from comment #5)
> > One issue with the SLSA4 checklist is that SLSA4 seems to be written in a
> > way that assumes developers are reviewing pull requests and there's a magic
> > forge that everyone trusts to securely decide when the merge criteria have
> > been met. Applying it to individual commits on a mailing-list workflow will
> > be tricky and AFAIK the kernel isn't currently doing that. The example on
> > SLSA4 website of a compliant project is SUSE Open Build System, which sounds
> > magic-forge-y.
> Yes, I think it is mostly used for "downstream" (distro like) projects where
> the upstream (signed) release tarball is used as trusted input and then any
> patches on top of that are treated at SLSA4 level.

SLSA v1.0 does not address source threats any more. It only deals with
dependency and build threats. So it just deals with "downstream" uses of
(trusted) releases.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2023-06-01 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 13:30 [Bug Infrastructure/29615] New: " fche at redhat dot com
2022-09-26 16:57 ` [Bug Infrastructure/29615] " serhei at serhei dot io
2022-09-26 17:20 ` serhei at serhei dot io
2022-09-26 17:39 ` ezannoni at gmail dot com
2022-09-27 11:45 ` mark at klomp dot org
2022-09-27 13:23 ` serhei at serhei dot io
2022-09-27 20:10 ` mark at klomp dot org
2023-06-01 19:54 ` mark at klomp dot org [this message]
2023-10-14  1:02 ` fche at redhat dot com

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).