libfido2 VS python-fido2

udev? yeah you should check that. https://github.com/Yubico/libfido2/blob/main/udev/70-u2f.rules Reload the udev rules after you change them if you do change them, and unplug the device, wait 15 seconds, plug it in again.

It's not extremely difficult at all to implement these! Heck, even at Google we use LibFido2 which is a free-to-use library (you can find it here if you want: https://github.com/Yubico/libfido2). Of course Google's version is a bit different and the creator of LibFido2 now works here, but all of these 2FA methods aren't particularly difficult to implement in the sense that most of the work (libraries, standards, exact specifications) is already done.

It could be possible yes. Libraries like https://github.com/Yubico/libfido2 already abstract away external keys (via CTAP) and the Windows WebAuthn API, which allows you to use Windows Hello for signing in using eg a Logitech Brio webcam.

https://fidoalliance.org https://loginwithfido.com https://w3.org/TR/webauthn-2/ https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html https://github.com/yubico/Python-Fido2 https://github.com/yubico/libfido2

They suggest using this libfido2 library to connect with the hardware devices. I don't really know much about OSS licenses and which are the most "free" so you'll have to decide that for yourself.

https://fidoalliance.org https://loginwithfido.com https://w3.org/TR/webauthn-2/ https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html https://github.com/yubico/Python-Fido2 https://github.com/yubico/libfido2

To start the migration process, let’s first replace u2f.start_authentication() with its counterpart. The data types that the WebAuthn API takes are not quite the same ones used in U2F API. In fact, one of the main pain points was converting the necessary fields into the correct data type.

The specification we'll be addressing says that if a user fails to identify himself/herself using his/her device's authenticator or external authenticator(s) supported by python-fido2, such user should be removed from the database, logged out of the application and then redirected to the registration page to restart the process. This is to ensure that only verified users who used the supported attestation formats during registration are authenticated and authorized.

Modern browsers support this awesome technology and there are a couple of its implemetations in various major programming languages and web frameworks, however, this multi-part post will only focus on implementing it in a Django application using a wonderful django application, django-mfa2 which utilizes python-fido2 under the hood.

But there seems to be somthing nearly finished. https://github.com/Yubico/python-fido2/blob/master/examples/server/server.py