• turmacar@lemmy.world
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    12 days ago

    The hash or a checksum can be sent to the page to be checked by the same function running in your browser that is checking if the new password has special characters etc.

    • Vigge93@lemmy.world
      link
      fedilink
      arrow-up
      11
      ·
      12 days ago

      That would be an extremely bad idea tho, because it would allow a malicious attacker to

      1. Try random usernames, and if the website returns a hash they know that user exists
      2. Once they have the hash, and the hashing algoritm, it is much easier to brute-force the password, bypassing any safeguards on the server

      Username/password validation should happen entirely server-side, with as little information as possible provided to the client

      • aesthelete@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        12 days ago

        Username/password validation should happen entirely server-side, with as little information as possible provided to the client

        💯

        It’s recommended practice to not even tell them which half of the username/password combination failed upon authentication failures.

    • testfactor@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      12 days ago

      Seems like a great way for me to harvest a bunch of hashes to pull down to my GPU rig and crack offline.