Let’s gooooooooo

  • eroc1990
    link
    English
    221 year ago

    Not a bad idea! The attack vector issue they mention in the PR comments is valid, though. Not displaying those errors gives an attacker no confirmation that a user whose account they’re trying to attack exists, if they’re trying known used passwords. But good on you doing what you can to contribute to the project!

    • Venator
      link
      fedilink
      181 year ago

      There should be an error, but it shouldn’t say whether it was the email or password that was wrong.

      • Spzi
        link
        fedilink
        English
        -2
        edit-2
        1 year ago

        An attacker would still know the account exists, and they would know the password did not match.

        Or you’re assuring them that specific password is used by some account, just not this one. Which is even worse.

        • Null User Object
          link
          fedilink
          English
          51 year ago

          Read the comment you’re responding to, again. Nothing about their suggestion leads to either of these scenarios.

          • Spzi
            link
            fedilink
            English
            41 year ago

            Right, I misread “shouldn’t” for “should”.

    • no banana
      link
      fedilink
      English
      6
      edit-2
      1 year ago

      Couldn’t they just check instancename/u/accountname to see if the user exists?

      • eroc1990
        link
        English
        31 year ago

        Theoretically yeah. Depends on how quickly the attacker is working or if they have enough information to know where the account lives. If they’re doing their due diligence, they could 100% confirm that. But if they aren’t, they might just go to a random instance, try logging in, and see if it works.

        By no means is it bad to offer a response, but it always risks giving an attacker more information than they need/the victim would want to have discovered about them.