Conversation

I don't know what point you're trying to make. If you want to go back to the original topic, it was me responding to whonix.org/wiki/OpenPGP#G and pointing out that an 100% Free Software hardware option with a deniable passphrase feature and on-device key gen with recovery exists.
2
It is dramatically less secure. That's the reality, sorry. It has massive attack surface and the proposed usage of encryption loses the nice properties of the passphrase implementation. You could of course use software with a similar approach on it but it doesn't change the rest.
1
Replying to and
If you feel this way and it fits your real world sec asumptions and models, enjoy It doesnt fit mine. Trezor is beyond any doubt, an excellent technical solution. It makes it but an excellent, one point failure HVT target, with high ROI potential for an attacker.
1
twitter.com/DanielMicay/st It's objectively far more secure against an online attack, offline attack or coercion than the proposed alternative. Running the Trezor firmware on hardware with an SoC more hardened against tampering would be a step up for offline attacks too.
Quote Tweet
Replying to @Ishan_Ishana @DusanDuda and 2 others
The proposed approach is objectively far less secure against an online attack, offline attack and coercion. A targeted attack on an individual is easier with a laptop. Your only argument is your theory that a supply chain attack on Trezor is more likely than $LAPTOP_VENDOR.
1
It seems to me that you just want to be a contrarian by focusing solely on the niche of supply chain attacks and ignoring that it's not clear cut. Ignoring the far more realistic, basic threat models shared by everyone (online attacks, coercion) doesn't make much sense to me.
1
You can say that but I can't understand focusing solely on a sophisticated supply chain attack while ignoring far more accessible and realistic attack vectors. Laptops are much more complex (many components) and aren't tamper evident so there's a lower bar for those attacks too.
2
Ideally, there would be a wider variety of hardware choices using the same model, i.e. tiny attack surface, high entropy seed with a great recovery mechanism, any number of deniable passphrases each deriving different keys, on-device confirmations and passphrase entry, etc.
1
1
It's not the hardware details of a Trezor that are compelling but rather the very well designed security model and the solid open source firmware implementation. The hardware is very boring / simple and it's straightforward to make a custom Trezor since it's all off-the-shelf.
1
1
The drawback compared to some alternatives is that they don't use a secure element since they want the firmware to be open source so it can be audited and so people can make alternate hardware implementations. It would add a bit more difficulty for offline attacks vs. the seed.
1
1
Show replies