Yubico Forum

Cool. Still wondering about client libraries though, to make it easier for developers to integrate into apps?

https://developers.yubico.com/u2f is this what you are looking for???

_________________
-Tom

Thanks for the clarification. However, I read the "ask for a refund" as "Too bad, go f**k yourself."



^ This is what I'm talking about. Carefully crafted wording, put in an obscure corner of the site. Carefully crafted, because a Google search for "YubiKey NEO U2F NFC" offers results that fly directly in the face of "Currently U2F does not support NFC."

I really do like my NEO. Honestly. If I come across as crass, it's because I have a hard time with shifty business practices and obviously-omitted product info in an attempt to boost sales. Just be honest with us up front, and the money will follow close behind that honesty.

As far as I can tell, the APDU format is already set and ready to go. The only things left to be defined are the AID and a way to indicate that the authentication occurred over NFC. Depending on how careful yubico was and how contrarian the working group is, it is entirely possible that once the U2F spec is announced that NFC with a ykneo will "just work".

In the worst case it would be pretty trivial for compliant NFC implementations to support the existing ykneo devices over NFC.

So sit tight for a bit and see how it plays out. Don't go returning your neo just yet.

I don't personally feel like the NFC U2F demo that Yubico release was intended as anything other than an engineering demonstration. I've only become aware of it from reading this forum. I don't think anything "shady" was intended. Yes, in retrospect, releasing it is confusing from a marketing perspective, but to attribute what is likely an honest mistake with some sort of marketing malice is, in my humble opinion, a mistake.

@SparkyXI: "I read the "ask for a refund" as "Too bad, go f**k yourself.""

IMHO, that kind of response is not only childish and inappropriate, but lowers the standards of our communication here. Please find somewhere else to deposit such bile in the future.

While I understand the basis of the frustration, offering a refund option is actually the only thing Yubico can offer in this situation. Clearly, it would NOT be in anyones interest if they were to compromise security just to be able to update firmware just to avoid such inconvenince. The principle of non-changeable firmware is much more important than that. Given that this aspect of the Yubikey design is long communicated very clearly, your response is totally malplaced, as we are all aware of the related potential consequences and "risk".

Go for the refund and consider not being at the forefront of development next time if you cannot withstand these perceived risks.

Yubikeys are multi-function devices that can serve several other (very practical) purposes too if you happen to keep it instead. It is a flexible product that comes with certain dilemmas, which is not unusual anywhere.

That said, Yubico can certainly learn from this and improve their communication anyway, especially at the sales pages, that should have more easily available information about dilemmas and adviseable considerations before purchase.

_________________
Regards,
Nomadus

By the way... I just noticed that, on recent Yubikey Neo devices, the U2F applet (Yubico U2F v1.1.0) now supports the new Fido U2F NFC AID:



...which is promising. This probably indicates that recent ykneos already support U2F NFC!

https://fidoalliance.org/specs/fido-u2f ... -selection

3.4 firmware NEOs, that is correct. Basically, NEOs manufactured since around mid-February 2015.