Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update newsletter #2

Open
cstuder opened this issue Mar 15, 2019 · 4 comments
Open

Update newsletter #2

cstuder opened this issue Mar 15, 2019 · 4 comments

Comments

@cstuder
Copy link

cstuder commented Mar 15, 2019

(Not sure if this is the right place to request this...)

I've just randomly stumbled across https://update.solokeys.com/ and updated my keys to 2.0.0.

As an end-consumer I didn't know about this webpage or any available firmware updates. I missed the note at the end of the last Kickstarter update mail.

I suggest setting up a dedicated update newsletter.

@nickray
Copy link
Member

nickray commented Mar 15, 2019

@cstuder we put it live just yesterday. An update to Kickstarter will go out, we'd like to gather more feedback before we do the "big announcement".

@0x0ece can you add the "updates" newsletter signup back to https://shop.solokeys.com so we have one non-developer place where people can register for updates (outside of KS).

@cstuder
Copy link
Author

cstuder commented Mar 15, 2019

Ah, so I really just stumbled across it. :-)

Well, as feedback goes: Update worked perfectly on Chrome 72 under Windows 10, even though there is an annoying repeated prompt from Chrome wanting permission to share the device name with the website. It reappeared with every user interaction.

And during the update process the other prompt ("Plug in your key and press the button.") seemed to get replaced by the same prompt whenever the percentage updated on the screen.

@nickray
Copy link
Member

nickray commented Mar 15, 2019

share device name

Should happen only once, it's necessary to determine the attestation key, and hence whether you have a secure or hacker Solo plugged in.

The upgrade path from pre-1.1.0 has some additional "oops timed out" due to the original key not having all commands.

replaced by the same prompt whenever the percentage updated on the screen.

Yes, that's a limitation of our "abuse" of the WebAuthn API to do the updates that you get these flashing popups. It's pretty funny, each browser has different opinions on what to flash when...

What happens is that usually in WebAuthn "user presence" (=button click) is verified for creating/signing keys, so browsers add a popup to signal action needed. For the update commands (which are our extension to WebAuthn), the key doesn't check user presence, so you have a flashing popup for each chunk of firmware that's written.

@nickray
Copy link
Member

nickray commented Sep 3, 2019

We haven't setup a release notification, I suggest using https://help.github.com/en/articles/watching-and-unwatching-releases-for-a-repository on the solokeys/solo repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants