• baltakatei@sopuli.xyz
    link
    fedilink
    arrow-up
    0
    ·
    4 hours ago

    It is not being fixed because the people that decide whether it needs fixing or not are so wealthy that they have dedicated servants to take care of that drudgery. You’re an NPC that is a programmable cog in their passive cash flow generator, not a person.

  • unphazed@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    11 hours ago

    My job uses a Yubikey, authenticator, and more than 6 passwords, one of which for some damn reason at random points in a day thinks I’m on a seperate machine and forces me to get a verification code in my email. On top of that, one password resets every 3mo, another at 3 weeks, and the others are like every 8mo. All remember past passwords, will not allow any variation or similarity (you had a twelve char password with a number at the end in 2021, try another). It is a damn struggle creating a new password 12 years in now.

    • DonJefe@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 hours ago

      Are you allowed to use a password manager, like 1password or Bitwarden? I juggle with docens of passwords per client, all with different expiration dates and complexity rules. A password manager is the only reason I can get them all straight. A good password manager should let you save your passwords, passkeys, recovery codes and MFA codes all in one app locked with a single password + MFA

  • Leviathan@fedinsfw.app
    link
    fedilink
    English
    arrow-up
    0
    ·
    11 hours ago

    I got a new phone and tried using the Merlin birding app but now I need to enter an email, receive an email, confirm using the link in the email…

    …and then enter the user name and password I’ve been using to log into the app for years.

    And it’s not just once but every time I use the app, it’s a nightmare, and I don’t want to give any extra information I don’t have to.

    • unphazed@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      11 hours ago

      Except you accept cookies in X browser, but not Y browser because that is an emulated system to run a 30yr old program they never bothered to update because it worked great on x86 machines but was never designed for 64 bit.

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        22 hours ago

        There are plenty of ways.

        DNS poisoning with one of those #4 private keys would be the easiest.

        Getting Grandma to add a trusted CA would be another.

        Paste bombs into browser terminals.

        Something you have is a very important part of keeping people out of your stuff.

        • Supercrunchy@programming.dev
          link
          fedilink
          arrow-up
          0
          ·
          21 hours ago

          Once they are at the level where they break HTTPS, they can also ask you for the 2FA code or passkey and intercept that through their services, and you’d be hacked anyway.

          • rumba@lemmy.zip
            link
            fedilink
            English
            arrow-up
            0
            ·
            20 hours ago

            Passkeys don’t work like that. They would, in fact, stop that from happening.

            That is of course if the company didn’t let you choose another method

            • Supercrunchy@programming.dev
              link
              fedilink
              arrow-up
              0
              ·
              20 hours ago

              I didn’t test it (of course), but I think they do for this case.

              So we have a man in the middle attack, that proxies traffic to a website through it and just decrypts it without changing it during the login. This is similar to what cloudflare does. The browser has no way to know somebody is spying: HTTPS cerificate is ok(stolen cert), the domain matches the expected(dns poisoning), even the page is exactly the same, so it performs the passkey challenge/response. The only thing that changed is the certificate, which is not suspicious (certificates can change normally!).

              The attacker is not able to clone the passkey, but they are able though to steal your session cookies after the login. Instead of giving you the “login success page” they keep you waiting on a loading page while they navigate (with a script) with your stolen session cookies to the “add passkey” page of the site to add theirs.

              If the website asks them again for the passkey as confirmation, instead of serving the “login successful page”, they serve the new 2FA prompt to you. You are left wondering “Didn’t I just do the 2FA? What a buggy site!”. And unknowingly approve adding the attacker’s passkey.

              Game over, account fully compromised.

              We are lucky that HTTPs is very good for security, they revoke certificates very quickly if this happens, and browsers check the certificate transparency logs making it impossible to forge a new certificate, even if you got hold of a root certificate with private key “4”. This attack also needs unrealistic level of compromise: stolen and unrevoked certificate + a poisoned DNS. Completely unrealistic scenario, but it’s not passkeys that saved you, it was HTTPS.

              When they say passkeys are unphisheable they mean you can’t usually copy them and give them to an attacker, but an attacker can absolutely still add theirs to your account.

  • AbsolutelyNotAVelociraptor@piefed.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    22 hours ago

    You forgot the “click to verify you are human” (followed by a dumb captcha, maybe 10) just after you click login but before logging in, which makes you, after you pass the captcha, click again to login.

  • Evotech@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    23 hours ago

    Nah fucking email code every time! Just let me use ausernsme and password fucking god damned it. I don’t want my email involved in this process!

  • nullspace@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    23 hours ago

    Your password is 30 days old. Make a new one. It can’t be the same as any of your last 37 passwords.