Yubico Forum

My previous post today about this issue (http://forum.yubico.com/viewtopic.php?f=26&t=1285) was dismissed and locked, without allowing me to reply. I purchased a $50 product (adding to my two Yubikeys I already own), and I expect more professionalism from Yubico.

First of all, to answer the admin's comment in the locked post, yes I have searched and read the other topics. The one topic, not "numerous", that was linked was this: http://forum.yubico.com/viewtopic.php?f=26&t=1032. This is the most recent post and the only post with any resolution, so I don't see how this is "numerous". Regardless, the instructions in there make no sense to me, and I don't see any official documentation from Yubico on how to do this correctly.

Second, it clearly says that "Windows Phone" is supported in the NEO product page. Nowhere does it say "if you don't understand how to install a Ubuntu VM to run command line scripts yourself, then don't buy a NEO". That just means it's not supported.

Back to the issue at hand. I would like to bring to attention the release notes for the latest Lastpass app currently in the Windows App Store: http://www.windowsphone.com/en-us/store/app/lastpass/9b86eadc-16e8-df11-9264-00237de2db9e: "Improved support for Yubikey NEO, so it is no longer necessary to reprogram it to use with this app.". Also, Lastpass documentation shows that Windows Phone 8 is supported: https://helpdesk.lastpass.com/security-options/multifactor-authentication-options/yubikey-authentication/#YubiKey+NEO+with+Windows+Phone+8+App. Are they talking about a different Yubikey NEO?

I have run the NDEF programming tool, and under the "NDEF payload", it only has the URI https://my.yubico.com/neo/. I believe it should have [OTP] appended to the end, but the tool does not have it, even when I reset it.

I hope you understand that this conflicting information is confusing; Does the NEO support Windows Phone 8 "out of the box"? Does the NEO support Nokia Lumia 920? Do I need to get an updated firmware for the NEO? Is Yubico aware that Lastpass claims the issue has been resolved?

If I need to contact Lastpass for support on the NEO, please tell me so. But please do not lock this post again, I believe I have made a valid argument that merits a discussion.

Hello Soylent,

Please send me an e-mail as private message where you would like to be contacted and we will address your issue directly.

Tom.

_________________
-Tom

Thanks Tom, will do. I apologize if I came off as rude in my post, I was already pretty frustrated by then. I originally just wanted to post here before opening a support ticket, in case anyone else is having the same issue. The forums are always the first place I look for support.

I would also like to know the answer.
I also bought 2 yubikey neo's based on the fact that LastPass and Yubico advertise it as working on Windows phone.

Hello,

Please anyone with the same issue, connect with support@yubico.com they will provide you with a refund if needed.

Tom.

_________________
-Tom

Tom,

In the response you gave in your previous thread you stated the problem was because of the current Microsoft implementation in Windows Phone to support NFC. Can you provide anymore details in what support the Neo needs and expects? Has the situation changed from Windows Phone 8.0 to 8.1 and latterly 8.1 update 1 and Nokia Cyan firmware?

Are Yubico communicating with Microsoft in anyway or is Neo seen as a Android only solution?

Many thanks

Paul

As far as we know it didn't changed.

We are not talking to any specific vendor specifically, we follow standards. If some manufactures uses a non standard protocol/implementation that we are likely to have some sort of integration problem with them.

_________________
-Tom

Tom,

You aren't being very helpful here. You state standards but don't expand on what you mean specifically and how Microsoft are implementing NFC against Android, Blackberry or Apple which doesn't meet the requirements of Yubico. Looking at the documentation from Microsoft they are opening up the capabilities of handsets and the OS to use NFC over time. Google approach is different but isn't without problems and causes security concerns. So if you can't articulate what you mean then I can't Tweet Joe Belfiore to ask him to improve the situation.

If your comments reflect the feeling of Yubico then maybe I need to look elsewhere for future solutions

Paul

The NEO is an ISO/IEC 14443-4 Smart Card, Mifare Classic 1K (emulated)

This backwards compatibility is not supported by windows phone, which doesn't recognize devices with multiple support.

This last time we checked. We would love to have the NEO working on Windows phone, however we can't do much about it. There are plenty of threads on this forum on the same topic.

Please read them, and you will see we released long ago a firmware hack for Windows phone with developers NEO edition. However this is not viable anymore.

mode_211
enable_trace

establish_context
card_connect
open_sc -security 1 -keyind 0 -keyver 0 -mac_key 404142434445464748494a4b4c4d4e4f -enc_key 404142434445464748494a4b4c4d4e4f

send_apdu -sc 1 -APDU 80e2800007df3504a5034420

card_disconnect
release_context

_________________
-Tom

Tom,

Thanks for the additional information which is much more helpful

Paul