[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <2XW7E21KHVYC6.30SSXH9R06ZEM@seraph.netsend.nl>
Date: Tue, 19 Nov 2019 15:37:23 +0100
From: Tim Kuijsten <info+oss-security@...send.nl>
To: oss-security@...ts.openwall.com
Subject: Re: Mitigating malicious packages in gnu/linux
> There is not a definitive solution here. But there are multiple efforts and
> research going on. The most important one, in my opinion, is the reproducible
> builds project [1]. We need to ensure we are not inserting random or
> non-deterministic data into our build artifacts. This stretches from upstream
> developers providing tarballs, to pre-compiled sources and packages from
> distributions. There is no distribution today that has full reproducible builds,
> but there are many projects that work towards this and work on reproducible
> builds.
One attack that is not solved by reproducible builds is one on the toolchain.
This can be solved with bootstrappable builds[1] which is about minimizing the
number of trusted binaries that are needed to produce the toolchain, that
produced the toolchain, ... that was used to build your package.
There was a talk this year called "Bitcoin Build System Security" by Carl Dong
about this topic[2].
[1] https://bootstrappable.org
[2] https://www.youtube.com/watch?v=I2iShmUTEl8
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
