Virtual authenticator?

[gaetanww]

Reading through the docs and especially (Readme.md):

Note that our python-fido2 fork will only connect to the software FIDO2 application, not a hardware authenticator. Install Yubico's fork to do that.

I understood that it was possible to build solo as a software virtual authenticator? Is that true? If so, what is the status on that? And how to build solo for PC only? For now I'm getting a lot of undefined functions issues.

Thank you for your help

[gaetanww]

I did some more digging around, so I'm goin g to answer part of my question:

• This project is supposed to build a "virtual authenticator" that interact with python-fido2 through udp. However, it is not currently building, see Travis
  I found the last commit that built successfully: Travis and built it without problem.

[nickray]

There is some code in pc/ that "simulates" a FIDO2 token, and is helpful for developing code (mainly, the FIDO2-specific logic, without the additional complication of embedded development). To interact with that, we forked Yubico's client library python-fido2, so you can interact with the "pc" implementation over UDP.

What are your expectations of a "virtual authenticator"? I am pretty sure this is not it.

[gaetanww]

Yes that is what I meant by "virtual authenticator", sorry for the confusing terminology.
It's just that make all didn't work on HEAD, because some functions aren't implemented in pc/device.c, so I was confused as to whether or not it was possible to run solo on linux (over UDP).

(Just to clarify, I used "virtual authenticator" because that is what google called it for their u2f implementation)

Thank you for your answer :)

[conorpp]

I added the missing functionality to pc/device.c and tested it works now (#33). It can be used as a software-only/virtual authenticator. It doesn't check for user presence and stores all state in local files. The counter and resident keys aren't stored, but that is relatively easy to add if needed.

[gaetanww]

Awesome, thanks!