Hacker News Reader

Comment by jamesnorden | Hacker News Reader

You're free to read the code and compile it yourself, I don't understand this question.

To trust the code you need to understand it, or trust someone else that understand it. I would not claim I can do that without spending a lot of time since I'm unfamiliar with the coreboot code base in the first place. Saying "you can just recompile yourself" is as useful as "you can cook deadly mushrooms yourself" instead of getting food poisoning from a 3rd party.

You say that like you or anyone else on the planet understands and trusts all the software they have running on their (phone/laptop/desktop).

That ship sailed a long time ago.

I think the idea is that all the people on the planet collectively can understand whether to trust all the software. The rest is comms.

Transparency breeds legitimacy.

Look, being able to look at the source of truth is the best you can hope for. Moreover, the project has been around for some time. If that's not enough, then fair, at the end of the day the choice is yours.

How would a person go from the sources posted on github to the binaries that get flashed? I don't see anything in https://github.com/MrChromebox that seems to be actual build scripts, without which the numerous other repos are less than useful

Switch on developer mode on a supported device, pop a shell, and run 'cd; curl mrchromebox.tech/firmware-util.sh --output firmware-util.sh; sudo bash firmware-util.sh'

For more detail, I point you toward the fine documentation

That's how you flash the precompiled binaries. I want to know how you make those binaries.

* ensure you have coreboot prereqs installed per doc.coreboot.org

* git clone https://github.com/MrChromebox/coreboot.git

* cd coreboot

* git submodule update --init --checkout --recursive

* make crossgcc-i386

* ./build-uefi.sh <name of board to build>

Reply on news.ycombinator.com