Just like apps and websites implement “Sign in with Apple” and Google couldn’t we build some kind of federated authentication provider? Then everyone creates an account there and fedi apps can implement an easy way to authenticate users. Even non fedi apps could use it. I imagine user interaction between different fediverse platforms would be much easier too.

I guess could run an auth instance. Ideally everyone would run their own, keeping your data safe.

Is there something likes this already? Saw some discussion here but not much else https://socialhub.activitypub.rocks/t/single-sign-on-for-fediverse/712

  • tomatol@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    7
    ·
    1 day ago

    Your password manager’s login can also get compromised

    • Saleh@feddit.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      13 hours ago

      Yeah it can. But then they have only my passwords. If they steal a database from a large identity provider, they have millions if not hundreds of millions of passwords. For monetarily motivated crime, my password manager is not a realistic target.

    • Captain Aggravated@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      ·
      21 hours ago

      It can, but is it likely to? To get my passwords, you’d need my KeePass database itself, which is only stored on computers I own. To unlock my password database, you need my password, which I have not stored digitally anywhere, and you’d need to have the keyfile. Oh which of the hundreds of thousands of files on my system is the keyfile?

      So you’ve gotten my password database open. Critical things like my lynchpin email address and banking accounts just aren’t in there. Those I memorize only. All of the “This would be bad if this got compromised” accounts have 2-factor authentication.

      Compared to breaking into a retailer or bank’s servers and getting hundreds of thousands if not millions of credentials, that’s a lot of effort to get one guy’s Lemmy account deets.

    • 4am@lemm.ee
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      22 hours ago

      So we should make a remote single point of failure, maintained by someone who probably isn’t a security expert or working on it full time?

      No, this is unfortunately the opposite of what we should be doing.

      EDIT: I should also add that people who make password managers literally focus on only that. They understand what they are making is a huge target and any of them worth their salt have independent audits and spend much of their time on design decisions related to security. Point being: typically the weakest link in a password manager is you. Set a good password, use a YubiKey or some other device, use 2FA, etc.

      • tomatol@lemm.eeOP
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        2
        ·
        1 day ago

        Not a single point but multiple points. Anyway I’m not gonna pretend I’m an expert in security! I just think it’s a feature worth exploring.

        • 4am@lemm.ee
          link
          fedilink
          English
          arrow-up
          2
          ·
          23 hours ago

          If someone runs an auth server, and I use it to identify me, and then it goes away, then I’m out of luck, my account is gone. This is the same problem we have now (with logins being tied to instances), except that it introduces a new place for a failure to occur. Rather than just relying on a lemmy instance, I also need to rely on an auth server to be maintained, safe, and secure.

          If I went to another auth server, then it’d give me a different identity and that would not make much sense.