Radoslav Gerganov

Correct, I have added support for pinAuth in the last version of the PR. The `solo key sign-file` also accepts `--pin` now.

I have implemented PGP signing with Solo and now I can sign git commits with my Solo Hacker! :tada: You can find the project here: https://github.com/rgerganov/solo-pgp The last two commits...

> Had a good look now @rgerganov. This is exactly how I imagined this should work :) > > If you have the time/energy, would be great to add your...

I have already added support for USB HID gadget in Solo, see this [Makefile](https://github.com/solokeys/solo/blob/master/tools/gadgetfs/Makefile). On Ubuntu you can simply run `make install` as root and this will create `/dev/hidg0`. The...

Rebased the patch and added support for pinAuth

> question is on what base we would run pin, basically force if available, or let the user decide some way on creating the credential or whatever I am trying...

I have rebased the patch on top of master

OpenSSH is using CTAP command 0x41 which is vendor specific to get the resident key. This is the log from Solo: ``` [HID] [HID] Recv packet [HID] CID: 00000006 [HID]...

I have implemented the commands which are used by OpenSSH for operating with resident keys. You can test my PR#392 with Solo Hacker. Any feedback is welcome!

Another way of testing the credential management functionality is with the `fido2-token` tool from `libfido2`: ``` $ fido2-token -L /dev/hidraw6 /dev/hidraw6: vendor=0x0483, product=0xa2ca (SoloKeys Solo 3.1.2-2-g423c580) $ fido2-token -I -c...