• Sonotsugipaa@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    24
    arrow-down
    3
    ·
    3 years ago

    Infuriating fact: if a service has maximum password length limits (lower than 1000 characters), they’re reversibly storing your password and if they’re that lazy it’s probably plain text

    • Sibbo@sopuli.xyz
      link
      fedilink
      arrow-up
      1
      ·
      3 years ago

      They may just base their limit on one or a few block sizes of the hash function.

      • kevincox@lemmy.ml
        link
        fedilink
        arrow-up
        7
        ·
        3 years ago

        That sounds incredibly unlikely. I would be good money that 99% of password length limits are not based on concrete limits. Things like “100 should be enough 🤷” must be way more common.

        I doubt 1% of programmers are away of their hashes block size. It is also probably irrelevant since after the first round everything is fixed size anyways.

    • Anemia@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      3 years ago

      Couldn’t it just be that they’re using something like bcrypt which won’t take any chars above its limit into account (knowing that there’s a limit will pretty much never matter to a user but why obscure the fact)? What does it even mean to store it reversibly, just because they have a char limit doesn’t mean they are encrypting the password, could just be some frontend shenannigans as well.

    • rubythulhu@beehaw.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 years ago

      Fun fact: Lemmy instances cap at 60. they’re not storing reversibly, they’re just using bcrypt and rather than pre-hashing the pw before bcrypt like most bcrypt users do, they just truncate to 60.

    • newsonic@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      3
      ·
      3 years ago

      Nope. No point in storing > 256 or even 128 chars for a password anyway. Useless storage wasted. Also it doesn’t really mean they store the password badly in the server.

      • conciselyverbose@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        3 years ago

        Ignoring that they must be hashed to be acceptable and that it’s not possible for 1000 characters of text to add up to a waste of storage worth mentioning in pretty much any environment, it’s literally impossible for a 128 character password limit to be beneficial in any way.

        A limit below that demonstrably lowers security by a huge margin.