Live data from Hacker News

Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

discourse.nixos.org

151–160 of 232 posts

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#151
post #146

Earlier quoted context omitted.

I don't really understand what you're saying. If you're saying "reproducible builds are reproducible", then that is obviously true, but the question is what is the benefit? Some people claim that the benefit is that there will be less incentive to threaten developers with violence, and I'm saying that's nonsense. If you cut through the nonsense, there are some modest claims that are true, but doing reproducible build…

> ... the question is what is the benefit? I don't think I should have to explain this. It has nothing directly to do with violence against developers, that's taking many leaps. It simply gives you what you expect, which is kinda the basis of safety and security.

> It has nothing directly to do with violence against developers, that's taking many leaps.

It is literally the very first claim on the front page of https://reproducible-builds.org.

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#152
post #151

Earlier quoted context omitted.

> ... the question is what is the benefit? I don't think I should have to explain this. It has nothing directly to do with violence against developers, that's taking many leaps. It simply gives you what you expect, which is kinda the basis of safety and security.

> It has nothing directly to do with violence against developers, that's taking many leaps. It is literally the very first claim on the front page of https://reproducible-builds.org .

That's just a bunch of marketing hype. I'm trying to stay focused closer to the matters at hand.

Perhaps my rambling on Development vs Distribution is relevant to the discussion? https://nixpulvis.com/ramblings/2021-02-02-signing-and-notar...

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#153
Recently, President Biden put out an executive order that mandates that NIST et al work out, over the next year, an SBOM/supply chain mandate for software used by Federal departments.

That's going to require the equivalent of "chain of custody" attestations along the entire build chain.

Along with SOC and PCI/DSS and other standards, this is going to require companies and developers to adopt NixOS type immutable environments.

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#154
post #153

Recently, President Biden put out an executive order that mandates that NIST et al work out, over the next year, an SBOM/supply chain mandate for software used by Federal departments. That's going to require the equivalent of "chain of custody" attestations along the entire build chain. Along with SOC and PCI/DSS and other standards, this is going to require companies and developers to adopt NixOS type immutable envi…

Unfortunately, I don't think this is going to be the outcome. We're more likely to end up with "Here is the list of filenames, subcomponents, and associated hashes" as opposed to requiring NixOS style environments. Vendors to the subcontractors will likely be required to provide the same list of filename/subcomponent/hashes, a far cry from repeatable builds.

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#155
post #135

Earlier quoted context omitted.

> I can't come up with a single benefit to security from reproducible builds. It is a means to allow to detect a compromised supply chain. If people rebuilding a distro cannot get the same hash as the distro shipping from the distributor, then likely the distributors infrastructure has been compromised

How does this work in practice? The distro is owned, so where are you getting the hash from? I mean, specifically, what does the attacker have control of and how does a repeatable build help me stop them.

The idea is that multiple independent builders build the same distro. You expect all of them to have the same final hash.

This doesn't help against the sources being owned, but it helps about build machines being owned.

Accountability for source integrity is in theory provided by the source control system. Accountability for the build machine integrity can be provided by reproducible builds.

To answer your specific questions: The attacker has access to the distro's build servers and is packaging and shipping altered binaries that do not correspond to the sources but instead contain added malware.

Reproducible builds allow third parties to also build binaries from the same sources and once multiple third parties achieve consensus about the build output, it becomes apparent that the distro's build infrastructure could be compromised.

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#157
post #155

Earlier quoted context omitted.

How does this work in practice? The distro is owned, so where are you getting the hash from? I mean, specifically, what does the attacker have control of and how does a repeatable build help me stop them.

The idea is that multiple independent builders build the same distro. You expect all of them to have the same final hash. This doesn't help against the sources being owned, but it helps about build machines being owned. Accountability for source integrity is in theory provided by the source control system. Accountability for the build machine integrity can be provided by reproducible builds. To answer your specific q…

OK so a build machine is owned and we have a sort of consensus for trusted builders, and if there's a consensus mismatch we know something's up.

I suppose that's reasonable. Sounds like reproducible builds is a big step towards that, though clearly this requires quite a lot of infrastructure support beyond just that.

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#158
post #96
post #11

This really deserves more love. Who remembers Ken Thompson's "Reflections on Trusting Trust"? The norm today is auto-updating, pre-built software. This places a ton of trust in the publisher. Even for open-source, well-vetted software, we all collectively cross our fingers and hope that whoever is building these binaries and running the servers that disseminate them, is honest and good at security. So far this has mo…

> I'm grateful to the nixos team for being beating a trail thru the jungle here. Retrofitting reproducibility onto a big software project that grew without it, is hard work. Actually, it's Debian guys who pushed reproducible build hard in the early days. They upstreamed necessary changes and also spread the concept itself. This is a two-decade long community effort. In turn, NixOS is mostly just wrapping those projec…

By the way, here's the stats on Debian's herculean share of the efforts: https://wiki.debian.org/ReproducibleBuilds

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#159
post #69

Earlier quoted context omitted.

Why does building from source help? It’s not like people are reading every line of the source before building it anyway 99.99% of the time.

If the package maintainer's build pipeline is compromised (eg. Solarwinds), you are unlikely to be affected if you build from reviewed source yourself.

Except hardly anyone reviews a single line of code.

Re: Nixos-unstable’s ISO_minimal.x86_64-Linux is 100% reproducible

#160
post #12

Mandatory link to the Debian single purpose site: https://isdebianreproducibleyet.com/ However that is for everything in Debian, not just the iso. It is truly remarkable to see all the Linux distributions move the needle forward.

And Arch Linux :) https://reproducible.archlinux.org/

[deleted]
Post reply on HN