running after a pip3 install and make init both fail after recent update to fido2 library about solo1-cli

[hasufell]

Half a year later, this project is still broken on pip.

[johnnyasantoss]

Manually pinning fido2 using pip3 install fido2==0.9.3 makes cli work again, but that's not ideal

[sseide]

applying the patch from @wuxxin fixed the issue. Can Solokeys please merge it and release a new version? should be 10 minutes work...
@0x0ece @conorpp @hoos97 @nickray

[GoetzGoerisch]

Ping @0x0ece @conorpp @hoos97 @nickray
Please update the current solo1-cli version. Thank you.

[gunterkoenigsmann]

For me the linked pull request resolves this issue and #153.

[johnnyasantoss]

Just downloaded in a new computer and got this error again (I remember reading this thread before)

[jhuylebroeck]

I'm not a coder myself, and I had a hard time resolving this issue. Thanks for the workaround, but I'd love a full update and solution.

[AWHubGit]

I'm not a coder myself, and I had a hard time resolving this issue. Thanks for the workaround, but I'd love a full update and solution.

Me too. Manually pinning fido2 using pip3 install fido2==0.9.3 makes cli working again, but I would like the latest version of the fido2 library.

Is it a secuirity flaw still to have CTAP1 class?

[shetyeshail]

I'm running into this issue as well. Pinning the pip fido2 library version to 0.9.3 as suggested by johnnyasantoss worked for me, but would appreciate an official patch to the solo1-cli tool. I believe the pull request from wuxxin would do the trick.

[tomash]

I'm also asking to update the current solo1-cli version, manual search-and-replace in installed pip package (or fixing fido2 to an old version) is a poor experience.