Independent verification of binary packages - reproducible builds
Independent verification system of binary packages.
rebuilderd monitors the package repository of a linux distribution and uses rebuilder backends like archlinux-repro to verify the provided binary packages can be reproduced from the given source code.
It tracks the state of successfully verified packages and optionally generates a report of differences with diffoscope for debugging. Note that due to the early state of this technology a failed rebuild is more likely due to an undeterministic build process instead of a supply chain compromise, but if multiple rebuilders you trust report 100% reproducible for the set of packages you use you can be confident that the binaries on your system haven't been tampered with. People are encouraged to run their own rebuilders if they can afford to.
Please see the setup instructions in the Arch Linux Wiki.
A rebuilder consists of the
rebuilderddaemon and >= 1 workers:
cd daemon; cargo run
Run a rebuild worker:
cd worker; cargo run connect http://127.0.0.1:8484
Afterwards it's time to import some packages:
cd tools; cargo run pkgs sync archlinux community \ 'https://ftp.halifax.rwth-aachen.de/archlinux/$repo/os/$arch' \ --architecture x86_64 --maintainer kpcyrd
--maintaineroption is optional and allows you to rebuild packages by a specific maintainer only.
To show the current status of our imported packages run:
cd tools; cargo run pkgs ls
To inspect the queue run:
cd tools; cargo run queue ls
Debian: pkg-config liblzma-dev libssl-dev libsodium-dev libsqlite3-dev
| Distro | Status | | ---------- | ------------ | | Arch Linux | Experimental | | Debian | Planned |
Development is currently funded by:
Please consider supporting the project.