From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About EGO_SUM
Date: Thu, 9 Jun 2022 19:49:04 +0200 [thread overview]
Message-ID: <a4602df9-e97c-3b3b-ce1e-e936cc1dfce7@gentoo.org> (raw)
In-Reply-To: <robbat2-20220608T184338-394361540Z@orbis-terrarum.net>
On 08.06.22 22:42, Robin H. Johnson wrote:
> EGO_SUM vs dependency tarballs:
> [..]
> - EGO_SUM is verifiable/reproducible from Upstream Go systems
Let's be explicit, there is a _security_ threat here: as a user of an
ebuild, dependency tarballs now take effort in manual review just to
confirm that the content full matches its supposed list of ingredients.
They are the perfect place to hide malicious code in plain sight. Now
with dependency tarballs, there is a new layer that by design will
likely be chronically under-audited. It gives me shivers, frankly.
Previously with a manifest and upstream-only URLs, only upstream can add
malicious code, not downstream in Gentoo.
Best
Sebastian
next prev parent reply other threads:[~2022-06-09 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:18 [gentoo-dev] About EGO_SUM Florian Schmaus
2022-06-03 12:56 ` Ionen Wolkens
2022-06-08 20:42 ` Robin H. Johnson
2022-06-09 6:18 ` [gentoo-dev] " Madhu
2022-06-09 17:49 ` Sebastian Pipping [this message]
2022-06-09 18:16 ` [gentoo-dev] " Anna
2022-06-09 18:33 ` John Helmert III
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=a4602df9-e97c-3b3b-ce1e-e936cc1dfce7@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox