Just unable to get this to work (macOS Monterey) #19
Replies: 6 comments 44 replies
-
It should not be necessary to install Rust / compile the Regarding the "old" Info.plist, I unfortunately don't have a Mac currently. If you can locate the existing Info.plist and replace it with the one included here (https://github.com/solokeys/solo2-cli/blob/main/Info.plist), I'm somewhat hopeful it might work. Would be great if some knowledgeable Mac users could chime in. |
Beta Was this translation helpful? Give feedback.
-
Quick update: Been working on the CTAP interface to get into the bootloader without requiring PCSC. Should be able to test on a Mac VM end of week and cut a release. |
Beta Was this translation helpful? Give feedback.
-
Would anybody like to test the macOS artifact on https://github.com/solokeys/solo2-cli/actions/runs/1639470266? That is, https://github.com/solokeys/solo2-cli/suites/4797767185/artifacts/134477432 |
Beta Was this translation helpful? Give feedback.
-
Hey @nickray, sorry to tag in on this discussion but I've been wondering about the state of the
|
Beta Was this translation helpful? Give feedback.
-
Hello, I'm having the same issue the OP was having (SoloKey not found). I have followed all the suggestions listed so far, including the detailed steps @felix-gohla provided. So far, nothing has worked to get solo2-cli to recognize the key. I'm using a MacBook Pro (Intel), Monterey 12.2.1, with a Solo2 Hacker v2.3.0 The key is visible in the System Report:
I start the PCSC daemon, then type "solo2 list" which gives the following output in the daemon's log:
Re-plugging the key only generates the "error getting plugin" messages. But when I try any command that requires access to the key, it reports no keys:
I was able to get the python script tests/basic.py to contact the key, display the device information, as well as set and reset the PIN, so I know the key is working!
I have no other smart card readers (unless touch-id counts?). Any help is appreciated! |
Beta Was this translation helpful? Give feedback.
-
Just here to provide update - on new Ventura 13 it's now working as it should. |
Beta Was this translation helpful? Give feedback.
-
Where to start? I'm trying to install this to test out my new Solo V2 keys, but I have not been able to get it to work.
I appreciate this is still in development, but it would be great if the installation instructions could be updated for a fresh install as it seems that things aren't fully explained to relatively inexperienced people (like myself I guess).
After some initial problems, I had to install Rust by running (as outlined here):
Then I managed to get
solo2
to install by running:However, when I run the following command:
I get:
Revisiting the README file, it mentions something about Solo 2 is supported by Ludovic Rousseau's CCID driver, but there has not been a release. The included Info.plist works.
Ok, so what does that actually mean to somebody who isn't very familiar with all this? I've tried to install Ludovic Rousseau's CCID driver by running:
As outlined here, I've also tried:
But the first command (
./MacOSX/configure
) results in:I have tried removing
libusb
(brew uninstall --ignore-dependencies libusb --force
) and trying again, which seems to progress further, but then results in:I have no idea what that means or what else to do on that so that runs into other problems and the rabbit hole deepens... Should I be doing something with the included Info.plist and if so, what and where?
In an ideal world, it would be great if the installation instructions were looked at again from a fresh installation point of view, so that any dependencies are detailed as it seems something isn't quite right here and I do not know what else to do to get this to work.
I'm running this on macOS Monterey (version 12.0.1) with cargo version 1.56.0 and solo2 version 0.1.0.
Beta Was this translation helpful? Give feedback.
All reactions