• ell1e@leminal.space
    link
    fedilink
    English
    arrow-up
    63
    arrow-down
    4
    ·
    21 hours ago

    People upvote because they hate change.

    People upvote because big tech has a tendency of forcing the most anti ownership outcome possible on everyone. Here, such an outcome likely would be mandatory passkeys that are set up to require hardware attestation.

    One way to reduce that risk is to boycott passkeys until TPM and hardware attestation are removed from the standard. You may not think that’s a fair response, or that such a boycott won’t save us from the inevitable outcome, but nevertheless it’s not a completely irrational reaction.

    • Aatube@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      5 hours ago

      It seems to me that the definition of attestation in the passkeys standard is the exact same as HTTPS certificates, which is not bad at all and nearly impossible to rug pull?

    • blackbrook@lemmy.ml
      link
      fedilink
      English
      arrow-up
      10
      ·
      16 hours ago

      And also until the committee designing it has it members on it representing the interests of users. The point that this was lacking in the original is-a-trap article is an important one and is also being missed.

    • NoLemurs@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      16 hours ago

      I’m just not convinced that mandatory hardware attestation is actually a real problem we need to worry about.

      Like, yes, people with high security jobs will have that for sure. And they should.

      But large companies that want customers? They want to make it as easy as possible for their customers to connect. They’re not going to force people to have a hardware device which if damaged or lost will lose them a customer. That’s just not what they want.

      • JustEnoughDucks@slrpnk.net
        link
        fedilink
        arrow-up
        6
        ·
        9 hours ago

        And yet, it’s there.

        Embrace, extend, extinguish as in literally every single corporate case. Thousands of rug pulls later and we still haven’t learned our lesson.

        In this case: first get people in the door en masse, then expand the requirements for things like hardware attestation in a transition period, then vendor lock people.

        Adobe would never move to cloud only, that would lose them customers.

        See: Literally every single API rug pull ever. Reddit, Unity, etc… Get people using the API and infrastructure, then switch from free to huge fees.

        See: cloud companies giving good deals for storage and then charging massive fees for output bandwidth to access or move that data

        See: VMware rug pull

        This is the exact same except they are telling us what they are going to do from the start. When someone tells you how shitty they are, listen.