An issue with the configuration COM API has been resolved where OATH-HOTP configurations with Yubikey 2.2 caused unexpected HOTPs to be generated. No problems with pre-2.2 keys.
From firmware version 2.2, the moving factor seed value can be set to an arbitrary value. The previous version of the configuration tool seeded this value with garbage/uninitialized data and as this field was not used prior to version 2.2, this issue was not noticed.
An updated version of the COM API has been uploaded to our web at
http://www.yubico.com/personalization-toolWe were also asked to provide a test vector for OATH HOTP. We suggest using the one from RFC 4226
3132333435363738393031323334353637383930
8-digit HOTPs from moving factor 0 shall then be
84755224
94287082
37359152
26969429
Regards,
JakobE
Hardware- and firmware guy @ Yubico
Login
FAQ
Search
