Yubico Forum

So I got a package of Limited Edition Plus Pack keys in the mail yesterday. Today I tried to enable U2F on the second slot, only to find that the Yubikey NEO Manager for Linux version 1.1.0 declares "The Yubikey NEO Manager doesn't support this device".

The ykneomgr application version 0.1.6(!?) invariably says "error: ykneomgr_discover_match (-4): Backend error" or something similar whenever I run it.

The yubikey-personalization-gui application version 3.1.18 (library 1.16.2) is the most useful one since it actually can read what type of device it is, configuration, firmware version (4.0.1), serial number, features supported. But I can't use it to enable U2F, can I?

How do I enable U2F for the Limited Edition Plus Pack keys?

My computer runs Trusty presently.

Hello,

Your device is already U2F enabled and it is not supported from the NEO manager.

Visit https://demo.yubico.com/u2f and test it out, be sure to have the latest stable version of Chrome installed

The Yubikey will have two slot as any other Yubikey, none of them is "occupied" by the U2F configuration.

be sure to add the device in your udev rule with this if you dont have it yet.
https://github.com/Yubico/yubikey-neo-m ... -ccid-udev

Ran the Python script. Seems to have done its job. I had already added the Udev rule though.

Chrome version used is :Version 40.0.2214.111 (64-bit)

Chrome extension installed: FIDO U2F (Universal 2nd Factor) extension 0.9.6

When asked to touch the flashing U2F device, there is a U2F device inserted, but it is not flashing. I touch it anyway, but predictably nothing happens.

$ lsusb
Bus 002 Device 003: ID 413c:2513 Dell Computer Corp. internal USB Hub of E-Port Replicator
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0c45:643f Microdia
Bus 001 Device 003: ID 413c:8197 Dell Computer Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 413c:5534 Dell Computer Corp.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 413c:2134 Dell Computer Corp.
Bus 003 Device 005: ID 1050:0410 Yubico.com
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

On an older Linux box running Ubuntu 12.04 and a slightly older Chrome version (.91) the FIDO U2F Chrome extension pops up a prompt asking if I want to allow access or not to the U2F device. On Trusty and Chrome version .111 there is no such prompt.

I can use the OTP feature with this key, but that is as far as I get presently.

Hmm, that is odd. I see now that the Python script has added a couple of new Yubico device entries beyond the 2 that was already there. But it doesn't look like 0x0410 has been added to the ifdProductId array as I suspect it should have.

do you have the extension?

https://chrome.google.com/webstore/deta ... ionmgcdmne

Yes I do and I did have it installed earlier as you can see in my previous post where I listed the version number of the Chrome extension.

I am at home now and I went through the procedure again. This time I restarted after adding the udev rule file. I ran "udevadm monitor" and it looked like the rule was picked up and used by udev. When I tried registering this time the key actually started flashing and registration succeeded when I touched it. The subsequent login also worked. Very nice.

So although the README file in /etc/udev/rules.d directory state that udevd monitors the directory using inotify, it doesn't seem to work, at least not reliably. A restart may be necessary. You may want to update the instructions on the site to show that. In Linux rebooting is normally not needed when installing software, but in this case it was. Running "sudo udevadm control --reload" may be an alternative.

For a moment I suspected that one of my other Chrome extensions like Adblock or Ghostery was causing issues. But thankfully not.

Mission accomplished. Thanks.