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

2 keys: 1 can be updated, the other not #102

Open
pjgueno opened this issue Mar 8, 2023 · 12 comments
Open

2 keys: 1 can be updated, the other not #102

pjgueno opened this issue Mar 8, 2023 · 12 comments

Comments

@pjgueno
Copy link

pjgueno commented Mar 8, 2023

I have an issue I can't understand:
I was given 2 solokeys and I was told I have to update them before use.
I followed the instructions and it works perfectly on the first key.

For the second key, I can see 1 blue bink only and then:
Screen Shot 2023-03-08 at 20 39 08

20:20200101.0 is under 2:20220822.0, isn't it ?

MacBook-3:SoloUpdates2 PJ$ solo2 update --verbose
Downloading latest release from https://github.com/solokeys/solo2/
Fetched firmware version 2:20220822.0 (2.964.0)
 INFO  solo2::transport > using CTAP as minimal transport
 INFO  solo2::transport > using CTAP as minimal transport
 INFO  solo2::device    > device fw version: 20:20200101.0
 INFO  solo2::device    > new fw version: 2:20220822.0
Firmware version on device higher than firmware version used.
This would be rejected by the device.
Error: Firmware rollback attempt

Can you explain me the issue.

When I plug the both keys:

MacBook-3:SoloUpdates2 PJ$ solo2 ls
Solo 2 1949AECA1525A256A384748B4189736D (CTAP only, firmware 2:20220822.0, locked)
Solo 2 FEB84FD1CFABCF59AD7F5C2BDBD8FEA9 (CTAP only, firmware 20:20200101.0)
MacBook-3:SoloUpdates2 PJ$ 

The first line is the key which was updated succesfully. Why is there this locked ?

@JohnLGalt
Copy link

Look at the first number.

20:20200101.0
2:20220822.0

20 > 2

@pjgueno
Copy link
Author

pjgueno commented Mar 8, 2023

But the key were given to me at the same time and the current firmware is 2... How can the 2nd key be higher than the current firmware ? The key doesn t blink or lights except once blue. Can I override ?

@pjgueno
Copy link
Author

pjgueno commented Mar 8, 2023

It means solo20 ! Instead of solo2...

@JohnLGalt
Copy link

I wonder if that is either a custom firmware, or else one of the keys you have is a 'hacker' edition.

@pjgueno
Copy link
Author

pjgueno commented Mar 10, 2023

It should be the hacker edition. It was from the kickstarter. Lukas from Sensor.Community who is always up to date (or state of the art?) give us 2 keys each. Unfortunately I have jsut one now...

@pjgueno
Copy link
Author

pjgueno commented Mar 10, 2023

I will have to wait 18 years...

@JohnLGalt
Copy link

Yeah, the hacker edition cannot be updated using the normal updates from my understanding.

I have one of each as well. I use the standard one all the time. The hacker edition is sitting here because I haven't learned it / figured it out yet.

@pjgueno
Copy link
Author

pjgueno commented Mar 12, 2023

The both keys are the same. The Update perfectly worked for the first. Maybe I will succeed to get a new key ...

@pjgueno
Copy link
Author

pjgueno commented May 10, 2023

Does anyone have the same issue?

@JohnLGalt
Copy link

Hacker edition is not the same as regular edition.

Look at your screenshots again - the Solo2 also shows "locked" after it. The Solo20 does not.

I suspect that while they look the same they actually are not.

@pjgueno
Copy link
Author

pjgueno commented May 10, 2023

image

@pjgueno
Copy link
Author

pjgueno commented May 10, 2023

I can't Tell more...
Both keys came in such carton stuff.

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