It seems like the password limit is set to 60 characters so I’m unable to login to my instance. There probably should be no limit in the app because each server could have different limits set.

    • woelkchen@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Computers get faster all the time, making brute force cracking of passwords easier all the time. Password managers don’t care how long a password is. The task of filling it out is the same.

      • Yer Ma@lemm.ee
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        60 character passwords with any amount of complexity would take effectively infinite time to brute, an 18 character password with complex characters would take millions of years… There is no reason to use 60, let alone more than

        • Amju Wolf@pawb.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Have you heard about pass phrases ?

          Also, none of those is a sane reason to limit password length. A huge point of hashing is having short, constant length strings on output no matter the input. There’s no limitation or database issue there.

          The only reason to limit password length is actually security (for bad algorithms) and DoS, but that requires a limit in the thousands.

  • micahmo@programming.devM
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Hi all,

    Continuing the discussion from GitHub… Here is the PR I opened.

    https://github.com/thunder-app/thunder/pull/766

    However, there’s still some discussion to be had about whether this is the right change.

    @snowe, a couple questions…

    Thanks!!

    • darklightxi@lemmy.worldM
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I believe Jerboa also has this character limit as mentioned in this PR. It seems like they truncate the password to take the first 60 characters if it’s too long. This is what Thunder also follows as of right now, except it’s shown explicitly to the user in the login modal