As always with open source projects, it might be a good idea to move it away from GitHub?
Could you please elaborate on to why?
21–25 of 25 posts
As always with open source projects, it might be a good idea to move it away from GitHub?
Could you please elaborate on to why?
Same comment as on the other MFA key story on the front page right now[0]: Sad that the form factor looks terrible compared to YubiKey Nano. It'd be really cool to have an "open" solution which comes in a minimally invasive package. For reference: https://i1.wp.com/vaultumllc.com/wp-content/uploads/2017/03/... [0] https://news.ycombinator.com/item?id=18036336
Right now it'd be a bit tough, because to fit our chipset [1] in that tight space, it would likely involve making a custom IC package [2] or placing silicon die's directly on the circuit. I think it'd be really cool to do that, and if we get enough sales/interesting, we'll definitely go that route.
Using something like the Tomu seems promising as well. It doesn't have the same security features and is just an M0 core, so it's not the best fit.
[1] https://i.imgur.com/sVQ34em.pnghttps://i.imgur.com/sVQ34em.p...
Same comment as on the other MFA key story on the front page right now[0]: Sad that the form factor looks terrible compared to YubiKey Nano. It'd be really cool to have an "open" solution which comes in a minimally invasive package. For reference: https://i1.wp.com/vaultumllc.com/wp-content/uploads/2017/03/... [0] https://news.ycombinator.com/item?id=18036336
If you get an ECAD/EDA tool you could do some work to reduce the size of the board. From what it looks like, you can squish things together by a lot still and replacing components could further reduce it. Though it's unlikely you'll be able to match the Yubi Nano easily unless you go for some expensive decisions (expensive unless you get a couple thousand keys).
Maybe one "affordable" idea could be to stack 2 two-layer PCBs XD.
We open sourced the firmware. To our knowledge this is the 1st open source implementation of FIDO2/CTAP2. Our firmware is designed to be run/developed without hardware, and we have implementations already for efm32 and nrf52840. We're actively working on a new port to SAM L11 that will use ARM TrustZone for improved security. There's still a lot to do on the ecosystem side. We'd like to improve tests, code style and…
Would be really great to have it on the upcoming RISC-V secure hardware, that should be released soon. Then we would have open hardware implementation of this on a open application core as well. Thank you so much for open sourcing this!
Earlier quoted context omitted.
Would be really great to have it on the upcoming RISC-V secure hardware, that should be released soon. Then we would have open hardware implementation of this on a open application core as well. Thank you so much for open sourcing this!
Are you involved in any ways? Do you know if there are developer previews available?
I don't know of that actually happening officially but probably you can.
See: https://keystone-enclave.org/
MIT worked before on Sanctum that you might want to look at, its sort of the pre-version of what keystone will be. See: https://eprint.iacr.org/2015/564.pdf