/SOLVED ( see in comments )

I'm experiencing what seems to be a WebAuthn/Passkey difficulty on Binance and want to know if anybody can reproduce it.

Surroundings

• OS: Linux Mint 22.3
• YubiKey: YubiKey 5 NFC
• Firmware: 5.7.4
• Browsers tested:
  • Courageous 1.92.143 (Chromium 150.0.7871.182)
  • Chromium 150.0.7871.124
• Each browsers produce the very same conduct.

Steps to breed

1. Log in to Binance.
2. Go to Security → Passkeys / Security Keys.
3. Add a brand new safety key utilizing the YubiKey.
4. The browser:
   • asks for the YubiKey FIDO2 PIN,
   • then the YubiKey LED begins blinking,
   • I touch the security key,
   • Binance studies that the important thing has been successfully added.
5. Binance instantly sends the confirmation e mail saying that a new passkey/security key has been added.

Every thing seems to complete efficiently.

Drawback

After logging out:

1. I enter my e mail tackle.
2. I click Continue with passkey.
3. The browser once more asks for the YubiKey PIN.
4. The YubiKey LED blinks.
5. I contact the important thing.
6. The browser returns:

Authentication all the time fails.

Further observations

• Binance displays the registered credential as:

  Safety Key on Linux Cross Gadget

which seems unusual for a USB YubiKey.

• Deleting the registered key from Binance additionally requires getting into the YubiKey PIN and touching the important thing, so Binance clearly acknowledges the YubiKey throughout delicate operations.

YubiKey verification

FIDO2 is enabled and working normally.

ykman information:

Gadget sort: YubiKey 5 NFC Firmware version: 5.7.four FIDO2: Enabled 

Resident credentials saved on the important thing:

google.com login.microsoft.com reddit.com 

No Binance credential is listed.

Different web sites (Google, Microsoft, Reddit) work appropriately with the same YubiKey.

What I've already examined

• Eliminated and recreated the key a number of occasions.
• Tried with the key already inserted and inserted through the course of.
• Tested with both Courageous and Chromium.
• Similar end result each time.

Query

Has anybody else on Linux experienced this?

Might this be a Binance WebAuthn challenge (credential creation not completing appropriately or RP ID mismatch), or is there a recognized compatibility concern with Linux browsers and Binance passkeys?

Any perception from the Binance group or users who've efficiently configured a YubiKey on Linux can be drastically appreciated.

/SOLVED ( see in comments )