Wallet Logo

Trezor One

Latest release: 1.10.5 ( 17th January 2022 ) 🔍 Last analysed 18th April 2022 . Reproducible when tested
29th July 2014

Jump to verdict 

Older reviews (show 4 of 4 reproducible)

Help spread awareness for build reproducibility

Please follow Trezor One and thank them for being reproducible  via their Twitter!

Disclaimer

The following Analysis is not a full code review! We plan to make code reviews available in the future but even then it will never be a stamp of approval but rather a list of incidents and questionable coding practice. Nasa sends probes to space that crash due to software bugs despite a huge budget and stringent scrutiny.

Do your own research!

Try out searching for "lost bitcoins", "stole my money" or "scammers" together with the wallet's name, even if you think the wallet is generally trustworthy. For all the bigger wallets you will find accusations. Make sure you understand why they were made and if you are comfortable with the provider's reaction.

If you find something we should include, you can create an issue or edit this analysis yourself and create a merge request for your changes.

The Analysis 

For the latest firmware version, we try the same as last time, wrapped into this script:

$ ./scripts/test/hardware/trezorOne.sh 1.10.5
...
Fingerprints:
b589b3a7d605b83094078f775f66d415a27d090abd3a31ccae7912a9d712a684 build/core/firmware/firmware.bin
7b432fe4e5d8fa4f00fe088ef449d63b4bc217c35c49f4d893508dc718aed220 build/core-bitcoinonly/firmware/firmware.bin
3e473d85eadbe6306deadd77f46547e076596507835e9cf6aafbb2ebeec2601b build/legacy/firmware/firmware.bin
61c418684cba2c9dc3db8f752a755feab2dea98df618cce6bf72750ae2ca6e21 build/legacy-bitcoinonly/firmware/firmware.bin

Hash of non-signature parts downloaded/compiled:
869d959bc3a6d9facdfb1993249cfd21d7657bc08c2b4e370fdac52057f8366c  -
869d959bc3a6d9facdfb1993249cfd21d7657bc08c2b4e370fdac52057f8366c  -

Hash of the signed firmware:
dfac7b21f88d3077ebba0928adb8c75040498379a77d5969136a15d1aa7978a9  trezor-1.10.5.bin

That is a match. This firmware is reproducible.

(lw)

Verdict Explained

The binary provided was reproducible from the code provided.

As part of our Methodology, we ask:

Does the binary we built differ from what we downloaded? If not, we tag it Reproducible

If we can reproduce the binary we downloaded from the public source code, with all bytes accounted for, we call the product reproducible. This does not mean we audited the code but it’s the precondition to make sure the public code has relevance for the provided binary.

If the provider puts your funds at risk on purpose or by accident, security researchers can see this if they care to look. It also means that inside the company, engineers can verify that the release manager is releasing the product based on code known to all engineers on the team. A scammer would have to work under the potential eyes of security researchers. He would have to take more effort in hiding any exploit.

“Reproducible” does not mean “verified”. There is good reason to believe that security researchers as of today would not detect very blatant backdoors in the public source code before it gets exploited, much less if the attacker takes moderate efforts to hide it. This is especially true for less popular projects.