Quote from: StockBet.com on September 09, 2017, 06:33:20 PM

This implies that you have to trust that the manufacturer doesn't have any rogue employees.

Much like you have to trust your OS maker doesn't have any rogue employees... or Intel/AMD... or the hard drive manufacturer... or the USB manufacturer... or the WiFi chipset manufacturer... or the RAM manufacturer... or the Ethernet manufacturer... or the Router/Modem manufacturer... or the

Trezor do their best, and you can verify the publicly viewable code is the one on your device...: https://github.com/trezor/trezor-mcu/blob/master/README.md#how-to-get-fingerprint-of-firmware-signed-and-distributed-by-satoshilabs

Quote from: StockBet.com on September 09, 2017, 07:47:02 PM

With Electrum, you run it on an offline computer or bootable USB and you sign the transaction there. Then you take the transaction to the online computer and broadcast the transaction. The private key never leaves your offline computer.

And what makes you think that a rogue version of Electrum wouldn't encode your private key in the OP_RETURN section of your transaction prior to signing it? What guarantee do you have that the version of Electrum you downloaded is the same as the code on Github?

You'll NEVER find a 100% secure solution... there are ALWAYS attack vectors... especially when humans are involved.