Yubico Forum

Actually there appears a later version (libykneomgr-0.1.2-win64.zip) but alas - same results.

Ok - bit the bullet and tried to compile the software contained at: https://github.com/Yubico/libykneomgr-dpkg as advised by Tom.
I used the latest version (0.1.3) - untarred it and executed the instructions contained on said webpage.
Initially the "./configure" bombed out due to a dependency on libzip, so installed that package (I am running debian 7 wheezy).
After this install I executed "./configure" again which appeared to run to completion without any error, BTW (as per instructions) it needs to be executed with option "--with-backend=pcsc" because otherwise it will try to compile with a non-existant windows library (ate least on my Wheezy) system which will not work.
Then executed "make check" which now bombs out with a fatal error on internal.h line 37 which refers to a missing winscard.h (apparently for a windows build).
I inspected this internal.h and found and on lines 32-38 #ifdefs for PCSC and (default) windows.
For a quick possible fix just to get it compiled removed #ifdefs lines 33, 36-38 in effect skipping the default winscard.h however it bombs out again but now on PCSC/wintypes.h so clearly I am missing some crucial sourcecomponent here.
@Tom as the question is now: how do I resolve this? Is it contained somewhere on github? Should I download another Yubico software package to resolve this? Or should I install some special package in the standard Debian 7 repository?

Please advise....

Thx in advance for any help on this and kind regards, Erik...

@diraimondo: you reported you compiled the software yourself.
I wonder whether you initially ran into the same compile problems as I did, and if so: how did you resolve it?

Thx in advance for your advice & kind regards, Erik...

I've used the AUR repository of Arch Linux: it does everything by itself.

Please use apt-get to install software https://launchpad.net/~yubico

Also, you have to touch the Yubikey NEO to inject the card correctly (check the device manager). Do this from Windows because your configuration under Linux doesn't look proper

_________________
-Tom

Ok Tom and others who addressed this topic(thx for your reactions so far).
The issue has been resolved now.
@Tom: like you suspected the issue was caused to my work PC.
Apparently (due to internal security constraints) it was unable to load the correct drivers for the NEO though this was not readily apparent other than the neo manager program reporting "error: ykneomgr_init (-4): Backend error".

I have installed the neo manager utility on a XP PC with no such restrictions and when I inserted the NEO after which the correct drivers were loaded.
I could then change the mode of my NEO back to HID+CCID+eject - I loaded the OATH applet using the NEO manager and then I loaded my key(s) using the desktop OATH utility.
When all was done I could then login into my google account using 2FA.
FYI I used the latest available neo manager (0.1.0)which can be downloaded from the Yubico GIT pages.

Once again thx for everyone's input and for those who encounter a similar issue it may be worthwhile the use the neo manager utility on a PC with less or no enforced hardware restrictions with regards to it's USB interfaces!

As I posted to https://aur.archlinux.org/packages/yubi ... nager-git/ you need pcscd running on Linux to resolve this.

Indeed all woes I had with my yubikey neo on my linux installation (now running debian 8/Jessie) turned out to be caused by pcscd not running.
In case other users of a yubikey neo experience issues with the neomanager or yubi authenticator you may want to check whether the pcscd daemon is running with:

Code:

/etc/init.d/pcscd status

If it is not running it is likely that the aformentioned utilities report the following errormessage: error:

Code:

ykneomgr_init (-4): Backend error

Once the daemon has been started with:

Code:

/etc/init.d/pcscd start

the utilities start to function correctly and the errormessage will not be reported again.
Hope this explanation may help those who have also encountered this issue.