Last week, I tried to register for a service and was really surprised by a password limit of 16 characters. Why on earth yould you impose such strict limits? Never heard of correct horse battery staple?

    • unmagical@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      Of course, but if you’re paying for network and processing costs you might as well cap it at something secure and reasonable. No sense in leaving that unbounded when there’s no benefit over a lengthy cap and there are potentially drawbacks from someone seeing if they can use the entirety of Wikipedia as their password.

      • DaPorkchop_@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        5 months ago

        You can also hash it on the client-side, then the server-side network and processing costs are fixed because every password will be transmitted using same number of bytes

        • unmagical@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          You still need to deal with that on the server. The client you build and provide could just truncate the input, but end users can pick their clients so the problem still remains.

    • phcorcoran@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      Sure but if my password is the entire lord of the rings trilogy as a string, hashing that would consume some resources