Responding from my phone since my computer is off and I'm about to sleep, my apologies for the bad formatting.
Glad to hear it works! Upstream has, as of a few hours ago, released a fix to yubikey-manager, I suspect nicoo will upload it tomorrow or some time soon. It is currently very early morning in their timezone ;). Taowa 10 Feb 2021 23:50:01 Jason Hernandez <saltthefr...@gmail.com>: > Hi Taowa, > > Thank you! I tested using the last six digits in the UI and that was accepted > by a login provider (Github). Hopefully upstream fixes this issue quickly. > Let me know if you want me to file a separate bug. I think the severity is > reduced with this workaround. > > Best regards, > Jason Hernandez (he/him) > > > On Wed, Feb 10, 2021 at 10:37 AM Taowa <ta...@debian.org> wrote: >> Hello, >> >> Jason Hernandez, 2021-02-10 10:03 -0500: >>> I believe the fix for this bug may be incomplete. >>> This version is generating 9-10 digit codes instead of the standard 6 digit >>> codes on my machine when using the CCID interface with a Yubikey NEO. These >>> 9-10 digit codes fail verification and make the package unusable. >> >> See the upstream bug at [1]. They're aware of the issue and working on a >> fix for it :). >> >> In the meantime, the report seems to suggest that the last six digits of >> the TOTP code generated are valid. If you have a moment, please try it >> and get back to me as to whether that's true. >> >> Thanks, >> Taowa >> >> >> [1] https://github.com/Yubico/yubioath-desktop/issues/693 >> >> -- >> Taowa (they) >> LOC FN35EM
