Build packages in a secure deterministic fashion inside a VM
Go to file
2011-03-19 18:09:36 -07:00
bin Make guest default to 10.0.2.2 as the apt mirror, fix skip_image vs quiet flags 2011-03-19 18:09:36 -07:00
libexec Make guest default to 10.0.2.2 as the apt mirror, fix skip_image vs quiet flags 2011-03-19 18:09:36 -07:00
target-bin multi-architecture builds 2011-01-31 23:50:59 -08:00
.gitignore use apt cacher, minor cleanup 2011-01-30 15:41:50 -08:00
README.md security mirror, command line commit specification 2011-02-01 09:48:33 -08:00

Gitian

Read about the project goals at the "project home page":https://gitian.org/ .

This package can do a deterministic build of a package inside a VM.

Deterministic build inside a VM

This performs a build inside a VM, with deterministic inputs and outputs. If the build script takes care of all sources of non-determinism (mostly caused by timestamps), the result will always be the same. This allows multiple independent verifiers to sign a binary with the assurance that it really came from the source they reviewed.

Synopsis:

Install prereqs:

sudo apt-get install python-vm-builder qemu-kvm apt-cacher
sudo service apt-cacher start

Create the base VM for use in further builds (requires sudo, please review the script):

bin/make-base-vm

Copy any additional build inputs into a directory named inputs.

Then execute the build using a YAML description file (can be run as non-root):

bin/gbuild <package>-desc.yml

or if you need to specify a commit for one of the git remotes:

bin/gbuild --commit <dir>=<hash> <package>-desc.yml

The resulting report will appear in result/<package>-res.yml

Poking around

  • Log files are captured to the var directory
  • You can run the utilities in libexec by running PATH="libexec:$PATH"
  • To start the target VM run start-target
  • To ssh into the target run on-target or on-target -u root
  • On the target, the build directory contains the code as it is compiled and install contains intermediate libraries
  • By convention, the script in <package>-desc.yml starts with any environment setup you would need to manually compile things on the target

TODO:

  • disable sudo in target, just in case of a hypervisor exploit
  • tar and other archive timestamp setter