Edit: @[email protected] solved it. It says “one special character”. Not “at least one”.

  • refalo@programming.dev
    link
    fedilink
    arrow-up
    28
    ·
    10 days ago

    Now imagine how many services just silently cut off your password at 8 characters and people never notice.

    UltraVNC is very guilty of this.

    • Buddahriffic@lemmy.world
      link
      fedilink
      arrow-up
      12
      ·
      10 days ago

      Once upon a time, battle.net passwords weren’t case sensitive. I used upper and lower case letters in my password then one day realized I didn’t hit shift for one of the caps as I hit enter out of habit, but then it still let me in instead of asking for the password again.

      It was disappointing because it takes more work to remove case-sensitivity than to leave it. I can’t think of any good reason to remove it. At least the character limit had a technical reason behind it: having a set size for fields means your database can be more efficient. Better to use the size of a hash and not store the password in plaintext, so it’s not a good reason, but at least it’s a reason.

      • lud@lemm.ee
        link
        fedilink
        arrow-up
        12
        ·
        edit-2
        10 days ago

        It’s possible that the passwords want through an old ass cobalt system or something that forced everything to be capitalized so to solve that they made everything non case sensitive.

        But even that sounds insane as the passwords should have been hashed.