mkinitcpio-ykfde VS libfido2

I am interested in running a self-signed Secure Boot LUKS setup that I could unlock with my YubiKey. I've tried an initramfs hook in my other devices and it works. However, I read this section about unlocking the LUKS partition with systemd and its integrated enrollment tool (systemd-cryptenroll) and my interest was piqued since it meant an integrated solution that doesn't depend on a third-party one.

Found a solution myself: https://github.com/eworm-de/mkinitcpio-ykfde/blob/master/README-dracut.md

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.