901
Stop Treating Phone Numbers As A Digital ID (notthesolution.substack.com)
submitted 2 years ago by to c/technology@lemmy.world
157 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 69 points 2 years ago (8 children)

I'm sad PGP didn't become a popular way to log into websites. A challenge-response protocol could have even been built into web browsers. Big tech is reinventing that idea as Passkey, but with a very big tech flavor.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [+] 34 points 2 years ago* (last edited 1 year ago) (7 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 24 points 2 years ago (6 children)

    I'm already hearing about restrictions on exporting passkeys and some apps requiring that you're not running a custom ROM on Android and stuff like that. Makes me worried they're going to fuck that up and make it restrictive bs

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 6 points 2 years ago (4 children)

    Why should my OS be any of their concern?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    I'm living this pain with a custom ROM already, with some banking stuff, Google Wallet, WhatsApp passkeys and I think Netflix (haven't installed it) block you for tripping up Google's security tests.

    If passkeys become a big thing and they'll start enforcing them and apps that have those security measures I'm going to fucking firebomb something. REEEEEE

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 2 years ago

    Passkeys or WebAuthn are an open web standard, and the implementation is flexible. An authenticator can be implemented in software, with a hardware system integrated into the client device, or off-device.

    Exportability/portability of the passkey is up to the authenticator. Bitwarden already exports them, and other authenticators likely do, too.

    WebAuthn relying parties (ie, web applications) make trust decisions by specifying characteristics of eligible authenticators & authentication responses & by checking data reported in the responses. Those decisions are left to the relying party's discretion. I could imagine locked-down workplace environments allowing only company-approved configurations connect to internal systems.

    WebAuthn has no bearing on whether an app runs on a custom platform: that's entirely on the developer & platform capabilities to reveal customization.

  • permalink
  • fedilink
  • source
  • parent