hoos97

Always enjoy this article when someone dusts it off and shares it anew. You have to appreciate the problem solving skills he demonstrated in order to pull of a viable fission reactor in the basement. The ultimate maker!

If it wasn't exploited makes it even better...shows that you are being aggressive in identifying issues and applying corrections. Take advantage of opportunities to show transparency in a good light as well as meet your commitments to be transparent when events have not gone your way. This shouldn't be about how many reports you have to issue. Google can afford the staff to make that happen.

Yes, because when you go public with the issue you are able to control the narrative. Bad judgement to assume that these issues will never reach the public eye. Especially knowing that a patched was successfully applied...instead Google looks like it is having trouble living up to it's Don't Be Evil motto.

You only have to leave the key in by choice. For example, I use my Solo to authenticate login for google. But, I only need it on login....which really doesn't happen very often from my laptop. So, I am not leaving my key embedded in my laptop, which presents a problem if you actually have your laptop lifted at Starbucks!

* SoloKeys (https://solokeys.com)

* Solo is the first open source security key to support the newest FIDO2 standard.

* Finishing prototype and preparing for production

* Launching Kickstarter tomorrow, Oct 3!

All comments and questions are appreciated.

This is cool...and I would back you in a kickstarter campaign...go for it!

Part of the value in the concept is the simplicity.