search

Yubico / yubikey-neo-manager

Cross platform personalization tool for the YubiKey NEO
https://developers.yubico.com/yubikey-neo-manager/
BSD 2-Clause "Simplified" License
57 stars 12 forks source link

token name and connection mode are not always shown properly #24

Closed FlorinAndrei closed 9 years ago

FlorinAndrei commented 10 years ago

YubiKey NEO Manager 0.2.4 OS X 10.9.5 MacBook Air NEO firmware 3.2

The token is already plugged in and has been used a few times as a smartcard for ssh authentication.

Then I launch the Manager. Sometimes (or rather often) the name of the token is not correctly displayed. I have a personalized name on this token. Instead, the default name is displayed.

Also, the connection mode is shown as CCID, while this token is configured as OTP+CCID.

If I keep the Manager running, unplug the token, then plug it back again, everything is displayed correctly. Sometimes I have to unplug/replug more than once.

FlorinAndrei commented 10 years ago

It's not easily reproducible, but it happens all the time, on and off.

It seems to appear more often if I use the token for a while, then decide to probe it with the Manager.

dainnilsson commented 10 years ago

Sounds like it might be related to Yubico/yubikey-personalization#55. The name of the token is just a local setting mapped to the serial of the device, so if the serial isn't correctly read the custom name won't display. I think this is an issue with the composite modes of the NEO, where access over one transport temporarily disables access over another, which might be causing the timeouts and other behavior you're seeing.

dainnilsson commented 9 years ago

Closing this as I haven't heard anything new. Assuming the problem is either fixed or the issue lies with how the host is engaging with the CCID connection.