5 ms·
Taking from the other sibling comment, this seems to be the sort of thing I mean: https://certificate.transparency.dev/howctworks/ https://certificate.transpar
by gaganyaan 5y ago
Taking from the other sibling comment, this seems to be the sort of thing I mean:
https://certificate.transparency.dev/howctworks/ https://certificate.transparency.dev/howctworks/
In your example, how do you handle updates when a certificate expires or needs to be revoked? The Yubikey won't have internet with that power budget, so you'll have to manually update it.
Whenever you update the Yubikey, just update it with a snapshot of whatever certificates you care about from a blockchain like the link above. The Yubikey itself doesn't have to be a fully-participating node.
- acdha 5y agoThat's certificate transparency, which few blockchain proponents seem to consider a blockchain — and the developers of Trillian definitely don't class it as such as per https://transparency.dev https://transparency.dev. I think that is a useful concept and that's not terribly far out of line with what I was proposing — the main idea was that the useful part is basically the chain of signatures for a transaction but that it's only worth so much infrastructure because so much of the system depends on real-world activity outside of it. If my driver signs receipt of your goods by having both of them wave a key over a phone, that is useful information but there's a cap on how much value you can see from it because it doesn't say whether those statements were honest. The types of blockchains proponents outline are too expensive for that but something like what CT does could be useful — the key part being that it's kept small, efficient, and allows offline operations to handle limited connectivity.