Yubico Forum

The previous personalizaton tool has ykUID field to specify "Unique (secret) Device ID". However, it seems that the new personalization tool does not have such field.

1. Is it correct there is no field for "Unique (secret) Device ID" anymore ?
2. If yes, what value is written by the new tool ? (it seems to be '000000')

The new personalization tool does not have the “ykUID” field to specify the "Unique (secret) Device ID". It is a design change and the value stored for the “ykUID” field in the YubiKey is “000000”.

I understand. Thanks for explanation.

Hello,

I don't really get it, is the use of the Device ID in the encrypted string removed completly?

If that's the case, why so? It felt pretty natural to identify the unique device (like the name of the field says ).

Maybe I'm missing something, but in my mind I was going to use that ID as a part of the authentication mechanism.
I wasn't going to use a shared AES-key among multiple devices, but if I was, that unique id was certainly a crucial detail.

Thanks in advance.

Yay, I'm some what more happy

Tried using the linuxtool (ykpersonalize), where I could set the unique id, for example. Also, set a longer whatever-that-unencrypter-string that's prepended is called, then what the Windows GUI allows for.

So a revised question; What's the deal with all the inconsistencies?

(On a side note, not related to this thread, I couldn't compile it successfully on x86_64, it suggested me building one of the libs with -fPIC, which made it compile but always segfaults when you try using the tool.)

I was just about to address the same issue. I have a usecase where i use one aes with several yubikeys and identify them with the secret id. But i guess that could be done with the public id too as long as the keys match the aes.

So if i got that right, the secret id will vanish in the future!?


Cheers Jochen

PLEASE do NOT remove the option to set your own 'secret' string

I use YK's in cooperation with client side certificates (CAcert signed ones). In my case, a client needs a (client side) certificate, a passprase and a YK which 'secret' matches a hash of the static data from the certificate. If I can't set the secret anymore, the link between the key and the certificate is broken..

The Secret ID field of the YubiKey is now used for validation of the OTP.

A new version of the Yubico Personalization tool for Windows (Beta) which allows to program the Internal User ID (Secret ID) and to add 10 MS, 20 MS and 30 MS intra-key pacing delay is now available for download. The installer and the user guide can be downloaded from:

http://www.yubico.com/developers/personalization/

I am happy to read that as of this release even Windows users can set their secret ID's again .

However, the first sentence puzzles me a bit. Has the factory programming been changed to include a Yubicom specific secret (and specific for that key, and random, one presumes?)