News for hackers. Stuff that matters.
Re:A new open security key: Solo v2 by amluto on Sunday January 03, 2021 @04:17PM (#25625331)
I see it supports firmware updates, and I see nothing about whether it uses an actual hardened secure element chip. I’m not convinced I would trust this device.

There’s a reason Yubikeys can’t be updated, and it’s not to sell more Yubikeys.

Re:A new open security key: Solo v2 by ecesena on Sunday January 03, 2021 @05:52PM (#25626025)
Yes to both.

We do support firmware upgrade, unlike other security keys. For example in 2020 we patched a couple security issues, while Yubico, Google Titan and Feitian all recalled keys. Specs and thus firmware are getting bigger and more complex, so we believe that updates are the only way to maintain security in the long run.

We do not use a secure element, unlike other keys. This is not a statement, it’s just a fact. If you want an open product, there’s no “secure element” available that doesn’t require an nda. We hope that our work (we’re not alone in this) will motivate manufacturer to release secure elements with less obscurity around them.

Re:A new open security key: Solo v2 by conorpp on Sunday January 03, 2021 @08:46PM (#25627143)
To add to this, we would like to be able to run open source & update-able code and leverage EAL certified secure elements. Chips like the SE050 have recently come on the market and will likely end up on our products eventually.
Re:A new open security key: Solo v2 by bsder on Sunday January 03, 2021 @05:54PM (#25626045)
Define "trust". Or more appropriately "threat model".

My biggest problem is not the key.

My biggest problem is the fact that I can't easily roll keys out in a startup with 5 people and not become the customer service IT person handling security problems every day.

Solve THAT problem and I'll pay a monthly fee for your service.

Re:A new open security key: Solo v2 by amluto on Sunday January 03, 2021 @09:07PM (#25627244)
Here’s my threat model: attacker gets physical access to the key for five minutes. They should not be able to break future uses of that same key without causing very obvious failures. If installing malicious firmware were to wipe the key, that would help some.
Re:A new open security key: Solo v2 by bsder on Sunday January 03, 2021 @09:22PM (#25627332)
> Here’s my threat model: attacker gets physical access to the key for five minutes.

That threat is so far off the typical path that it can't even see civilization anymore.

However, simply encasing the key in acrylic would solve your use case.

These keys are meant to solve the typical remote attacks like phishing--and they do that extremely well.

They also are quite good at stopping the: "Someone stole my laptop and now has access to everything." If the key is on your keychain, that scenario is stopped cold.

These keys are not really meant to solve one-to-one attacks by determined adversaries. And, to be fair, such an adversary is going to compromise your OpSec LONG before he tries to compromise your key.