mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl via ptxdist <ptxdist@pengutronix.de>
To: "Alexander Dahl via ptxdist" <ptxdist@pengutronix.de>,
	"Alexander Dahl" <ada@thorsis.com>,
	"Sven Püschel" <s.pueschel@pengutronix.de>
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [PATCH] xz: version bump 5.8.1 -> 5.8.4
Date: Mon, 21 Sep 2026 08:18:04 +0200	[thread overview]
Message-ID: <20260921-granola-stimulus-1fd65d7980e8@thorsis.com> (raw)
In-Reply-To: <aq40OBCdDZgbO-gH@pengutronix.de>

Hello Michael,

Am Sat, Sep 19, 2026 at 09:05:28AM +0200 schrieb Michael Olbrich:
> On Mon, Sep 14, 2026 at 05:00:55PM +0200, Alexander Dahl via ptxdist wrote:
[…]
> > Notes:
> >     Not sure what security gain we have from tarballs created by GitHub?
> 
> It helps detecting supply chain attacks. The "make dist" archive is
> basically impossible to reproduce, so we need to trust the uploader that it
> was not modified. For the git tarball, all changes are visible in the
> commit history. While someone still needs to look, it's much easier to spot
> something.
> And that is not theoretical: The xz backdoor did just that with a modified
> build-to-host.m4.
> 
> >     This just makes packaging harder.
> 
> I'm not sure what you mean with that.

Usually upstream publishes sha256 sums and gpg signatures along a
tarball release.  I usually check those, and compare with the sums
other distributions (e.g. buildroot) have in their packages.  If we
take the generated tarball from git, those checks are impossible.

Greets
Alex



  reply	other threads:[~2026-09-21  6:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 15:00 Alexander Dahl via ptxdist
2026-09-19  7:05 ` Michael Olbrich
2026-09-21  6:18   ` Alexander Dahl via ptxdist [this message]
2026-09-22 10:10     ` Sven Püschel

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=20260921-granola-stimulus-1fd65d7980e8@thorsis.com \
    --to=ptxdist@pengutronix.de \
    --cc=ada@thorsis.com \
    --cc=s.pueschel@pengutronix.de \
    /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