You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had Yubikey 1.0.4 / 1.0.5 installed and working for some time. It's been awesome! I wanted to update to 1.1.0 to take advantage of some new features. When I attempted to do so, I could no longer login. With debugging enabled, I see the following:
May 18 12:08:31 dev yk_chkpwd: Encryption Key: TICKET_ENC_KEY_BEGIN|{HEX}|TICKET_ENC_KEY_END
May 18 12:08:31 dev yk_chkpwd: crc invalid: 0xa280
May 18 12:08:31 dev yk_chkpwd: public_uid has no length, OTP is invalid
Are the older databases created around the time of Yubikey 1.0.4/1.0.5 no longer compatible with 1.1.0? If so, is there a work around? Or do I need to recreate my /etc/yubikey files everywhere?
Thanks!
The text was updated successfully, but these errors were encountered:
Hello!
I've had Yubikey 1.0.4 / 1.0.5 installed and working for some time. It's been awesome! I wanted to update to 1.1.0 to take advantage of some new features. When I attempted to do so, I could no longer login. With debugging enabled, I see the following:
May 18 12:08:31 dev yk_chkpwd: Encryption Key: TICKET_ENC_KEY_BEGIN|{HEX}|TICKET_ENC_KEY_END
May 18 12:08:31 dev yk_chkpwd: crc invalid: 0xa280
May 18 12:08:31 dev yk_chkpwd: public_uid has no length, OTP is invalid
Are the older databases created around the time of Yubikey 1.0.4/1.0.5 no longer compatible with 1.1.0? If so, is there a work around? Or do I need to recreate my /etc/yubikey files everywhere?
Thanks!
The text was updated successfully, but these errors were encountered: