mirror of
https://github.com/dashpay/dash.git
synced 2024-12-26 12:32:48 +01:00
aec7441ac2
751549b52a9a4cd27389d807ae67f02bbb39cd7f contrib: guix: Additional clarifications re: substitutes (Carl Dong) cd3e947f50db7cfe05c05b368c25742193729a62 contrib: guix: Various improvements. (Carl Dong) 8dff3e48a9e03299468ed3b342642f01f70da9db contrib: guix: Clarify SOURCE_DATE_EPOCH. (Carl Dong) 3e80ec3ea9691c7c89173de922a113e643fe976b contrib: Add deterministic Guix builds. (Carl Dong) Pull request description: ~~**This post is kept updated as this project progresses. Use this [latest update link](https://github.com/bitcoin/bitcoin/pull/15277#issuecomment-497303718) to see what's new.**~~ Please read the `README.md`. ----- ### Guix Introduction This PR enables building bitcoin in Guix containers. [Guix](https://www.gnu.org/software/guix/manual/en/html_node/Features.html) is a transactional package manager much like Nix, but unlike Nix, it has more of a focus on [bootstrappability](https://www.gnu.org/software/guix/manual/en/html_node/Bootstrapping.html) and [reproducibility](https://www.gnu.org/software/guix/blog/tags/reproducible-builds/) which are attractive for security-sensitive projects like bitcoin. ### Guix Build Walkthrough Please read the `README.md`. [Old instructions no. 4](https://github.com/bitcoin/bitcoin/pull/15277#issuecomment-497303718) [Old instructions no. 3](https://github.com/bitcoin/bitcoin/pull/15277#issuecomment-493827011) [Old instructions no. 2](https://github.com/bitcoin/bitcoin/pull/15277#issuecomment-471658439) <details> <summary>Old instructions no. 1</summary> In this PR, we define a Guix [manifest](https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-package.html#profile_002dmanifest) in `contrib/guix/manifest.scm`, which declares what packages we want in our environment. We can then invoke ``` guix environment --manifest=contrib/guix/manifest.scm --container --pure --no-grafts --no-substitutes ``` To have Guix: 1. Build an environment containing the packages we defined in our `contrib/guix/manifest.scm` manifest from the Guix bootstrap binaries (see [bootstrappability](https://www.gnu.org/software/guix/manual/en/html_node/Bootstrapping.html) for more details). 2. Start a container with that environment that has no network access, and no access to the host's filesystem except to the `pwd` that it was started in. 3. Drop you into a shell in that container. > Note: if you don't want to wait hours for Guix to build the entire world from scratch, you can eliminate the `--no-substitutes` option to have Guix download from available binary sources. Note that this convenience doesn't necessarily compromise your security, as you can check that a package was built correctly after the fact using `guix build --check <packagename>` Therefore, we can perform a build of bitcoin much like in Gitian by invoking the following: ``` make -C depends -j"$(nproc)" download && \ cat contrib/guix/build.sh | guix environment --manifest=contrib/guix/manifest.scm --container --pure --no-grafts --no-substitutes ``` We don't include `make -C depends -j"$(nproc)" download` inside `contrib/guix/build.sh` because `contrib/guix/build.sh` is run inside the container, which has no network access (which is a good thing). </details> ### Rationale I believe that this represents a substantial improvement for the "supply chain security" of bitcoin because: 1. We no longer have to rely on Ubuntu for our build environment for our releases ([oh the horror](72bd4ab867/contrib/gitian-descriptors/gitian-linux.yml (L10)
)), because Guix builds everything about the container, we can perform this on almost any Linux distro/system. 2. It is now much easier to determine what trusted binaries are in our supply chain, and even make a nice visualization! (see [bootstrappability](https://www.gnu.org/software/guix/manual/en/html_node/Bootstrapping.html)). 3. There is active effort among Guix folks to minimize the number of trusted binaries even further. OriansJ's [stage0](https://github.com/oriansj/stage0), and janneke's [Mes](https://www.gnu.org/software/mes/) all aim to achieve [reduced binary boostrap](http://joyofsource.com/reduced-binary-seed-bootstrap.html) for Guix. In fact, I believe if OriansJ gets his way, we will end up some day with only a single trusted binary: hex0 (a ~500 byte self-hosting hex assembler). ### Steps to Completion - [x] Successfully build bitcoin inside the Guix environment - [x] Make `check-symbols` pass - [x] Do the above but without nasty hacks - [x] Solve some of the more innocuous hacks - [ ] Make it cross-compile (HELP WANTED HERE) - [x] Linux - [x] x86_64-linux-gnu - [x] i686-linux-gnu - [x] aarch64-linux-gnu - [x] arm-linux-gnueabihf - [x] riscv64-linux-gnu - [ ] OS X - [ ] x86_64-apple-darwin14 - [ ] Windows - [ ] x86_64-w64-mingw32 - [ ] Maybe make importer for depends syntax - [ ] Document build process for future releases - [ ] Extra: Pin the revision of Guix that we build with with Guix [inferiors](https://www.gnu.org/software/guix/manual/en/html_node/Inferiors.html) ### Help Wanted [Old content no. 3](https://github.com/bitcoin/bitcoin/pull/15277#issuecomment-483318210) [Old content no. 2](https://github.com/bitcoin/bitcoin/pull/15277#issuecomment-471658439) <details> <summary>Old content no. 1</summary> As of now, the command described above to perform a build of bitcoin a lot like Gitian works, but fails at the `check-symbols` stage. This is because a few dynamic libraries are linked in that shouldn't be. Here's what `ldd src/bitcoind` looks like when built in a Guix container: ``` linux-vdso.so.1 (0x00007ffcc2d90000) libdl.so.2 => /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/libdl.so.2 (0x00007fb7eda09000) librt.so.1 => /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/librt.so.1 (0x00007fb7ed9ff000) libstdc++.so.6 => /gnu/store/4sqps8dczv3g7rwbdibfz6rf5jlk7w90-gcc-5.5.0-lib/lib/libstdc++.so.6 (0x00007fb7ed87c000) libpthread.so.0 => /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/libpthread.so.0 (0x00007fb7ed85b000) libm.so.6 => /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/libm.so.6 (0x00007fb7ed6da000) libgcc_s.so.1 => /gnu/store/4sqps8dczv3g7rwbdibfz6rf5jlk7w90-gcc-5.5.0-lib/lib/libgcc_s.so.1 (0x00007fb7ed6bf000) libc.so.6 => /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/libc.so.6 (0x00007fb7ed506000) /gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fb7ee3a0000) ``` And here's what it looks in one of our releases: ``` linux-vdso.so.1 (0x00007ffff52cd000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f87726b4000) librt.so.1 => /usr/lib/librt.so.1 (0x00007f87726aa000) libm.so.6 => /usr/lib/libm.so.6 (0x00007f8772525000) libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f877250b000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f8772347000) /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f8773392000) ``` ~~I suspect it is because my script does not apply the gitian-input patches [described in the release process](https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#fetch-and-create-inputs-first-time-or-when-dependency-versions-change) but there is no description as to how these patches are applied.~~ It might also be something else entirely. Edit: It is something else. It appears that the gitian inputs are only used by [`gitian-win-signer.yml`](d6e700e40f/contrib/gitian-descriptors/gitian-win-signer.yml (L14)
) </details> ### How to Help 1. Install Guix on your distro either [from source](https://www.gnu.org/software/guix/manual/en/html_node/Requirements.html) or perform a [binary installation](https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html#Binary-Installation) 2. Try out my branch and the command described above! ACKs for top commit: MarcoFalke: Thanks for the replies. ACK 751549b52a9a4cd27389d807ae67f02bbb39cd7f laanwj: ACK 751549b52a9a4cd27389d807ae67f02bbb39cd7f Tree-SHA512: 50e6ab58c6bda9a67125b6271daf7eff0ca57d0efa8941ed3cd951e5bf78b31552fc5e537b1e1bcf2d3cc918c63adf19d685aa117a0f851024dc67e697890a8d
230 lines
8.0 KiB
Markdown
230 lines
8.0 KiB
Markdown
# Bootstrappable Bitcoin Core Builds
|
|
|
|
This directory contains the files necessary to perform bootstrappable Bitcoin
|
|
Core builds.
|
|
|
|
[Bootstrappability][b17e] furthers our binary security guarantees by allowing us
|
|
to _audit and reproduce_ our toolchain instead of blindly _trusting_ binary
|
|
downloads.
|
|
|
|
We achieve bootstrappability by using Guix as a functional package manager.
|
|
|
|
## Requirements
|
|
|
|
Conservatively, a x86_64 machine with:
|
|
|
|
- 2 or more logical cores
|
|
- 4GB of free disk space on the partition that /gnu/store will reside in
|
|
- 24GB of free disk space on the partition that the Bitcoin Core git repository
|
|
resides in
|
|
|
|
> Note: these requirements are slightly less onerous than those of Gitian builds
|
|
|
|
## Setup
|
|
|
|
### Installing Guix
|
|
|
|
If you're just testing this out, you can use the
|
|
[Dockerfile][fanquake/guix-docker] for convenience. It automatically speeds up
|
|
your builds by [using substitutes](#speeding-up-builds-with-substitute-servers).
|
|
If you don't want this behaviour, refer to the [next
|
|
section](#choosing-your-security-model).
|
|
|
|
Otherwise, follow the [Guix installation guide][guix/bin-install].
|
|
|
|
> Note: For those who like to keep their filesystems clean, Guix is designed to
|
|
> be very standalone and _will not_ conflict with your system's package
|
|
> manager/existing setup. It _only_ touches `/var/guix`, `/gnu`, and
|
|
> `~/.config/guix`.
|
|
|
|
### Choosing your security model
|
|
|
|
Guix allows us to achieve better binary security by using our CPU time to build
|
|
everything from scratch. However, it doesn't sacrifice user choice in pursuit of
|
|
this: users can decide whether or not to bootstrap and to use substitutes.
|
|
|
|
After installation, you may want to consider [adding substitute
|
|
servers](#speeding-up-builds-with-substitute-servers) to speed up your build if
|
|
that fits your security model (say, if you're just testing that this works).
|
|
This is skippable if you're using the [Dockerfile][fanquake/guix-docker].
|
|
|
|
If you prefer not to use any substitutes, make sure to set
|
|
`ADDITIONAL_GUIX_ENVIRONMENT_FLAGS` like the following snippet. The first build
|
|
will take a while, but the resulting packages will be cached for future builds.
|
|
|
|
```sh
|
|
export ADDITIONAL_GUIX_ENVIRONMENT_FLAGS='--no-substitutes'
|
|
```
|
|
|
|
Likewise, to perform a bootstrapped build (takes even longer):
|
|
|
|
```sh
|
|
export ADDITIONAL_GUIX_ENVIRONMENT_FLAGS='--bootstrap --no-substitutes'
|
|
```
|
|
|
|
### Using the right Guix
|
|
|
|
Once Guix is installed, deploy our patched version into your current Guix
|
|
profile. The changes there are slowly being upstreamed.
|
|
|
|
```sh
|
|
guix pull --url=https://github.com/dongcarl/guix.git \
|
|
--commit=82c77e52b8b46e0a3aad2cb12307c2e30547deec \
|
|
--max-jobs=4 # change accordingly
|
|
```
|
|
|
|
Make sure that you are using your current profile. (You are prompted to do this
|
|
at the end of the `guix pull`)
|
|
|
|
```bash
|
|
export PATH="${HOME}/.config/guix/current/bin${PATH:+:}$PATH"
|
|
```
|
|
|
|
> Note: There is ongoing work to eliminate this entire section using Guix
|
|
> [inferiors][guix/inferiors] and [channels][guix/channels].
|
|
|
|
## Usage
|
|
|
|
### As a Development Environment
|
|
|
|
For a Bitcoin Core depends development environment, simply invoke
|
|
|
|
```sh
|
|
guix environment --manifest=contrib/guix/manifest.scm
|
|
```
|
|
|
|
And you'll land back in your shell with all the build dependencies required for
|
|
a `depends` build injected into your environment.
|
|
|
|
### As a Tool for Deterministic Builds
|
|
|
|
From the top of a clean Bitcoin Core repository:
|
|
|
|
```sh
|
|
./contrib/guix/guix-build.sh
|
|
```
|
|
|
|
After the build finishes successfully (check the status code please), compare
|
|
hashes:
|
|
|
|
```sh
|
|
find output/ -type f -print0 | sort -z | xargs -r0 sha256sum
|
|
```
|
|
|
|
#### Recognized environment variables
|
|
|
|
* _**HOSTS**_
|
|
|
|
Override the space-separated list of platform triples for which to perform a
|
|
bootstrappable build. _(defaults to "i686-linux-gnu x86\_64-linux-gnu
|
|
arm-linux-gnueabihf aarch64-linux-gnu riscv64-linux-gnu")_
|
|
|
|
> Windows and OS X platform triplet support are WIP.
|
|
|
|
* _**SOURCES_PATH**_
|
|
|
|
Set the depends tree download cache for sources. This is passed through to the
|
|
depends tree. Setting this to the same directory across multiple builds of the
|
|
depends tree can eliminate unnecessary redownloading of package sources.
|
|
|
|
* _**MAX_JOBS**_
|
|
|
|
Override the maximum number of jobs to run simultaneously, you might want to
|
|
do so on a memory-limited machine. This may be passed to `make` as in `make
|
|
--jobs="$MAX_JOBS"` or `xargs` as in `xargs -P"$MAX_JOBS"`. _(defaults to the
|
|
value of `nproc` outside the container)_
|
|
|
|
* _**SOURCE_DATE_EPOCH**_
|
|
|
|
Override the reference UNIX timestamp used for bit-for-bit reproducibility,
|
|
the variable name conforms to [standard][r12e/source-date-epoch]. _(defaults
|
|
to the output of `$(git log --format=%at -1)`)_
|
|
|
|
* _**V**_
|
|
|
|
If non-empty, will pass `V=1` to all `make` invocations, making `make` output
|
|
verbose.
|
|
|
|
* _**ADDITIONAL_GUIX_ENVIRONMENT_FLAGS**_
|
|
|
|
Additional flags to be passed to `guix environment`. For a fully-bootstrapped
|
|
build, set this to `--bootstrap --no-substitutes` (refer to the [security
|
|
model section](#choosing-your-security-model) for more details). Note that a
|
|
fully-bootstrapped build will take quite a long time on the first run.
|
|
|
|
## Tips and Tricks
|
|
|
|
### Speeding up builds with substitute servers
|
|
|
|
_This whole section is automatically done in the convenience
|
|
[Dockerfiles][fanquake/guix-docker]_
|
|
|
|
For those who are used to life in the fast _(and trustful)_ lane, you can use
|
|
[substitute servers][guix/substitutes] to enable binary downloads of packages.
|
|
|
|
> For those who only want to use substitutes from the official Guix build farm
|
|
> and have authorized the build farm's signing key during Guix's installation,
|
|
> you don't need to do anything.
|
|
|
|
#### Authorize the signing keys
|
|
|
|
For the official Guix build farm at https://ci.guix.gnu.org, run as root:
|
|
|
|
```
|
|
guix archive --authorize < ~root/.config/guix/current/share/guix/ci.guix.gnu.org.pub
|
|
```
|
|
|
|
For dongcarl's substitute server at https://guix.carldong.io, run as root:
|
|
|
|
```sh
|
|
wget -qO- 'https://guix.carldong.io/signing-key.pub' | guix archive --authorize
|
|
```
|
|
|
|
#### Use the substitute servers
|
|
|
|
The official Guix build farm at https://ci.guix.gnu.org is automatically used
|
|
unless the `--no-substitutes` flag is supplied.
|
|
|
|
This can be overridden for all `guix` invocations by passing the
|
|
`--substitute-urls` option to your invocation of `guix-daemon`. This can also be
|
|
overridden on a call-by-call basis by passing the same `--substitute-urls`
|
|
option to client tools such at `guix environment`.
|
|
|
|
To use dongcarl's substitute server for Bitcoin Core builds after having
|
|
[authorized his signing key](#authorize-the-signing-keys):
|
|
|
|
```
|
|
export ADDITIONAL_GUIX_ENVIRONMENT_FLAGS='--substitute-urls="https://guix.carldong.io https://ci.guix.gnu.org"'
|
|
```
|
|
|
|
## FAQ
|
|
|
|
### How can I trust the binary installation?
|
|
|
|
As mentioned at the bottom of [this manual page][guix/bin-install]:
|
|
|
|
> The binary installation tarballs can be (re)produced and verified simply by
|
|
> running the following command in the Guix source tree:
|
|
>
|
|
> make guix-binary.x86_64-linux.tar.xz
|
|
|
|
### When will Guix be packaged in debian?
|
|
|
|
Vagrant Cascadian has been making good progress on this
|
|
[here][debian/guix-package]. We have all the pieces needed to put up an APT
|
|
repository and will likely put one up soon.
|
|
|
|
[b17e]: http://bootstrappable.org/
|
|
[r12e/source-date-epoch]: https://reproducible-builds.org/docs/source-date-epoch/
|
|
|
|
[guix/install.sh]: https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh
|
|
[guix/bin-install]: https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html
|
|
[guix/env-setup]: https://www.gnu.org/software/guix/manual/en/html_node/Build-Environment-Setup.html
|
|
[guix/substitutes]: https://www.gnu.org/software/guix/manual/en/html_node/Substitutes.html
|
|
[guix/substitute-server-auth]: https://www.gnu.org/software/guix/manual/en/html_node/Substitute-Server-Authorization.html
|
|
[guix/inferiors]: https://www.gnu.org/software/guix/manual/en/html_node/Inferiors.html
|
|
[guix/channels]: https://www.gnu.org/software/guix/manual/en/html_node/Channels.html
|
|
|
|
[debian/guix-package]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850644
|
|
[fanquake/guix-docker]: https://github.com/fanquake/core-review/tree/master/guix
|