Yubico Forum

I just bought a yubikey neo with firmware v3.4.9 and configured it for OATH HOTP and configured NDEF to work on the slot with the OATH HOTP (I've tried this in both slot 1 & 2 with the exact same results).

On my Android phone, OnePlus One, I installed yubiclip v1.2.0.

When I touch the key to the back of my phone, yubiclip gets the OTP *BUT* every 8 digit OTP is proceeded by the letter "p". For example:

p36780753

Have I stumbled upon a bug? Any ideas on how to stop each OTP from being proceeded with a "p"

[UPDATE]
I rebooted my OnePlus One a few dozen more times and the "p" went away.

This was just NFC weirdness on my Android and had nothing to do with the NEO or YubiClip.

I can't reproduce using ANY of the settings within the OATH-HOTP programming section of the Personalization Tool. The only way I can get a "p" prefix is by going to Tools > NDEF Programming, changing URI to Text, adding a p in the NDEF payload textbox, and clicking Program.

thanks for testing this, much appreciated.

I programmed NDEF as "text" and no matter what I put into the payload field (including "p"), yubiclip would not recognize the yubikey. yubiclip will only recognize my neo when NDEF is programmed as "URI" with "https://my.yubico.com/neo/" in the payload field.

I believe the neo is capable of transmitting 2 kinds of RTD's (Record Type Definitions): RTD_URI & RTD_TEXT

Does Yubiclip support RTD_TEXT definitions?

Change it back to the default settings of URI. With YubiClip installed it will intercept the HOTP.

understood.

Here's the real issue:

"When I touch the key to the back of my phone, yubiclip gets the OTP *BUT* every 8 digit OTP is proceeded by the letter "p". For example:

p36780753"

Three of us have just tried this on new NEOs with three different phone models (new and old). Go back to the default settings:

Tools > NDEF Programming
select desired configuration slot
URI
NDEF Payload - https://my.yubico.com/neo/
Program

Again, the only way we've been able to add a single random character to the beginning of the OTP is by programming with the Text option, and adding a character to the NDEF Payload field. Text is not the default selection.

appreciate y'all helping out so quickly.

I was asking about the RTD's that yubclip accepts because I suspect this is an issue with my phone and this would be confirmed if we're 100% sure that yubiclip accepts RTO_TEXT. If yubiclip does not accept RTD_TEXT then I still wouldn't be sure what the problem is.

Thanks again for the responses

I rebooted my OnePlus One a few dozen more times and the "p" went away.

This was just NFC weirdness on my Android and had nothing to do with the NEO or YubiClip.