Help pls. Exchange ask me to sign my adresses (MICA), could you please add a signing fonction into Ledger Wallet?

Hi,

Would be greatly appreciated if ledger could implement a fonction into ledger wallet, to sign our adresses. For us, the plebs, it's a difficult procedure.

( I am unable to sign with my taproot BTC adress, but i managed to sign with my segwit BTC adress, using sparrow 2.5.3).

Don´t know why sparrow can sign segwit but not taproot.
(seed on the ledger , connected to sparrow)

reddit.com
u/machin_bidule — 11 days ago
▲ 0 r/DroneCombat+1 crossposts

Sodium into the incendiary drones? WB Storage depots.

Sodium burns when touched by water.

Just wondering : what would happens if incorporated into the drone charge.

( I know nothing about the mass / cost / handling risk / risk of pollution / war laws. )

That's just a question.

reddit.com
u/machin_bidule — 13 days ago

Possible WebAuthn / Passkey bug on Linux with YubiKey 5 NFC

/SOLVED ( see in comments )
I'm experiencing what appears to be a WebAuthn/Passkey issue on Binance and would like to know if anyone can reproduce it.

Environment

  • OS: Linux Mint 22.3
  • YubiKey: YubiKey 5 NFC
  • Firmware: 5.7.4
  • Browsers tested:
    • Brave 1.92.143 (Chromium 150.0.7871.182)
    • Chromium 150.0.7871.124
  • Both browsers produce the exact same behavior.

Steps to reproduce

  1. Log in to Binance.
  2. Go to Security → Passkeys / Security Keys.
  3. Add a new security key using the YubiKey.
  4. The browser:
    • asks for the YubiKey FIDO2 PIN,
    • then the YubiKey LED starts blinking,
    • I touch the security key,
    • Binance reports that the key has been successfully added.
  5. Binance immediately sends the confirmation email saying that a new passkey/security key has been added.

Everything appears to complete successfully.

Problem

After logging out:

  1. I enter my email address.
  2. I click Continue with passkey.
  3. The browser again asks for the YubiKey PIN.
  4. The YubiKey LED blinks.
  5. I touch the key.
  6. The browser returns:

>

Authentication always fails.

Additional observations

  • Binance displays the registered credential as:Security Key on Linux Cross Device

which seems unusual for a USB YubiKey.

  • Deleting the registered key from Binance also requires entering the YubiKey PIN and touching the key, so Binance clearly recognizes the YubiKey during sensitive operations.

YubiKey verification

FIDO2 is enabled and working normally.

ykman info:

Device type: YubiKey 5 NFC
Firmware version: 5.7.4
FIDO2: Enabled

Resident credentials stored on the key:

google.com
login.microsoft.com
reddit.com

No Binance credential is listed.

Other websites (Google, Microsoft, Reddit) work correctly with the same YubiKey.

What I've already tested

  • Removed and recreated the key multiple times.
  • Tried with the key already inserted and inserted during the process.
  • Tested with both Brave and Chromium.
  • Same result every time.

Question

Has anyone else on Linux experienced this?

Could this be a Binance WebAuthn issue (credential creation not completing correctly or RP ID mismatch), or is there a known compatibility issue with Linux browsers and Binance passkeys?

Any insight from the Binance team or users who have successfully configured a YubiKey on Linux would be greatly appreciated.

/SOLVED ( see in comments )

reddit.com
u/machin_bidule — 29 days ago

Possible WebAuthn / Passkey bug on Linux with YubiKey 5 NFC

I'm experiencing what appears to be a WebAuthn/Passkey issue on Binance and would like to know if anyone can reproduce it.

Environment

  • OS: Linux Mint 22.3
  • YubiKey: YubiKey 5 NFC
  • Firmware: 5.7.4
  • Browsers tested:
    • Brave 1.92.143 (Chromium 150.0.7871.182)
    • Chromium 150.0.7871.124
  • Both browsers produce the exact same behavior.

Steps to reproduce

  1. Log in to Binance.
  2. Go to Security → Passkeys / Security Keys.
  3. Add a new security key using the YubiKey.
  4. The browser:
    • asks for the YubiKey FIDO2 PIN,
    • then the YubiKey LED starts blinking,
    • I touch the security key,
    • Binance reports that the key has been successfully added.
  5. Binance immediately sends the confirmation email saying that a new passkey/security key has been added.

Everything appears to complete successfully.

Problem

After logging out:

  1. I enter my email address.
  2. I click Continue with passkey.
  3. The browser again asks for the YubiKey PIN.
  4. The YubiKey LED blinks.
  5. I touch the key.
  6. The browser returns:

>

Authentication always fails.

Additional observations

  • Binance displays the registered credential as:

​

Security Key on Linux
Cross Device

which seems unusual for a USB YubiKey.

  • Deleting the registered key from Binance also requires entering the YubiKey PIN and touching the key, so Binance clearly recognizes the YubiKey during sensitive operations.

YubiKey verification

FIDO2 is enabled and working normally.

ykman info:

Device type: YubiKey 5 NFC
Firmware version: 5.7.4
FIDO2: Enabled

Resident credentials stored on the key:

google.com
login.microsoft.com
reddit.com

No Binance credential is listed.

Other websites (Google, Microsoft, Reddit) work correctly with the same YubiKey.

What I've already tested

  • Removed and recreated the key multiple times.
  • Tried with the key already inserted and inserted during the process.
  • Tested with both Brave and Chromium.
  • Same result every time.

Question

Has anyone else on Linux experienced this?

Could this be a Binance WebAuthn issue (credential creation not completing correctly or RP ID mismatch), or is there a known compatibility issue with Linux browsers and Binance passkeys?

Any insight from the Binance team or users who have successfully configured a YubiKey on Linux would be greatly appreciated.

reddit.com
u/machin_bidule — 29 days ago