Great to see that the guide is completed. @w4tsn thought I should have got it to work. What seems to have happened is that there is a way that I either changed the Yubikey programming so that it is no longer recognizable in lsusb (“Yubikey not found”) or there is a way to remotely deprogram Yubikeys. The Yubikey was fully functional at first. Learning about the difference between HMAC-SHA1 (which Yubikey C Bio does not have) and FIDO 2FA (which has to do with confirming synchronized timing as I understand that) was interesting.
Precisely how did you configure? I mentioned earlier that there a differences between the guide and the structure I am looking at on my system. You might unpack this but I am still at the point of putting the article into practice. Like I said, I don’t know why my key goes unrecognized by the Authenticator and lsusb/lspci when it was working fine before. Last thing I had it plugged into was login.gov, which must be the vector, and now it is inert. How is that possible?
In response to the article, first I should mention that the type of Yubikey (C Bio) might be what is causing the difficulty. C Bio cannot be reset to factory defaults according to the company. The guides I referred to above didn’t use clevis. There are probably either details I have to work out that are not discussed in the more non-specific level of the guides or C Bio has particularities.