Thought I may add this update:- I updated my neo manager to 1.0.0 to test out the OTP+U2F+CCID functionality (Although, apparently my Distro's Chromium package is still on v38, so, I'll have to wait to test this as I don't feel like compiling Chromium myself), while messing around in the neo manager I did spot these errors floating around in the command line:-
Code:
$ neoman
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/neoman/model/jsapi.py", line 66, in send_apdu
return self._neo.send_apdu(apdu.decode('hex')).encode('hex')
File "/usr/lib/python2.7/site-packages/neoman/model/neo.py", line 40, in inner
return func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/neoman/device_ccid.py", line 104, in send_apdu
byref(buf_size)))
File "/usr/lib/python2.7/site-packages/neoman/device_ccid.py", line 62, in check
raise YkNeoMgrError(status)
neoman.exc.YkNeoMgrError: ykneomgr error: -4
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
LOG [OpenPGP]: ERROR req: 00f10000, resp: 6985
As I normally run neomanager from dmenu (A little tool that launches applications, sort of like the 'run' dialog on Windows) I've never really seen the std{out,err} of neoman. The neoman interface works fine, even with these errors/exceptions, but, obviously something is going on behind the scenes that even your own software can't deal with, unfortunately, I don't know the APDU command list, so, I don't know what the actual commands it's issuing are, nor what the response is.