Edit: @Successful_Try543@feddit.org solved it. It says “one special character”. Not “at least one”.

    • marcos@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      When you enter an apostrophe, and the site returns a 500 response stating you are trying to attack it. (And yeah, it’s always 500, not 400.)

    • Malgas@beehaw.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      I used to use a system that was perfectly happy to let you use a semicolon when setting the password, but then login would fail if you did.

  • __init__@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    If you have to try really hard to meet their password requirements, that’s how you know it’s super secure.

  • refalo@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    2 months 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
      0
      ·
      2 months 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
        0
        ·
        edit-2
        2 months 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.

      • NotAnOnionAtAll@feddit.org
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        At least the character limit had a technical reason behind it: having a set size for fields means your database can be more efficient.

        If that is the actual technical reason behind it, that is a huge red flag. When you hash a password, the hash is a fixed size. The size of the original password does not matter, because it should not be stored anyway.

        • Buddahriffic@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          2 months ago

          Correct, hence the sentence after the one you quoted :)

          If any service can recover your password and send it back to you rather than just resetting it for you to set a new one, don’t rely on that service for anything you want to keep secure. And certainly don’t reuse a password there, though you shouldn’t be reusing passwords anyways because who knows what they are and aren’t storing, even if they don’t offer password recovery.

          • NotAnOnionAtAll@feddit.org
            link
            fedilink
            arrow-up
            0
            ·
            2 months ago

            Sorry, didn’t want this to look like an attack or disagreement. Just wanted to highlight that point, because arbitrary maximum sizes for passwords are a pet peeve of mine.

            • Buddahriffic@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              2 months ago

              Yeah no worries and agreed. I hate seeing commercial sites using worse password sanitization practices than I used for my first development website that wasn’t even really intended for anyone else to log in to and any max length suggests the password is either stored or processed in plaintext.

              IMO it should even be hashed on the client side before being sent so that it doesn’t show up as plaintext in any http requests or logs. Then salted and hashed again server side before being stored (or checked for login).

              • SpaceCowboy@lemmy.ca
                link
                fedilink
                arrow-up
                0
                ·
                2 months ago

                IMO it should even be hashed on the client side before being sent so that it doesn’t show up as plaintext in any http requests or logs. Then salted and hashed again server side before being stored (or checked for login).

                But if someone got that hashed version they could hack the client to have client side hashing code just send that hashed value to the server. You’d want to have the server to send a rotating token of some sort to use for encrypting the password on the client and then validate it on the server side that it was encrypted with the same token the server sent.

                Seems complicated to me… https is probably has good enough encryption, so eh, whatever.

      • Veloxization@yiffit.net
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        I got past it because it happened to throw a place from my country. And there was also a flagpole with a flag on it to really drive it home. XD

      • chiliedogg@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        Last time I got pretty deep in, but it became impossible when the chess notation rule required Cs and Ds, making it impossible to stay below the roman numberal sum limit.

      • seang96@spgrn.com
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        I used Google lens. Got stuck afterwards on a chess rule. The captcha rule used the notation for the chess one to complicate it further haha

      • xoggy@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        problem is the late stages of the game the password requirements change when your password’s emojis start catching fire.

        • Raxiel@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          2 months ago

          I put that out but the stupid chicken choked while I was looking for a YouTube video 4:42 long

  • FuglyDuck@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    My guess is they mean, one capital letter, one lower case letter, a number, and a special character

    what’s always amused me about these rules is that they exist because people are dumb. Technically, they lower the difficulty of the passwords slightly. ( for example, knowning that one character is a number reduces it to 10 options in stead of 10+26+26+whatever set of special characters)

    anyhow. people should use password managers. just saying.

  • Matriks404@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Your Internet Banking Password should one special character (~!@#%^&*)

    Great grammar on their part.

  • corsicanguppy@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 months ago

    Please tell me someone didn’t buy software with ‘atleast’ spelled like that in there. Please, tell me someone tested the web app and had the brains God gave a douglas fir and knew that wasn’t a word; that it was never a word; that the writer’s spell check should have picked that up; that it’s not been over-ruled by stupid so much that it just takes it.

  • TheSealStartedIt@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 months ago

    This was a new one for me:

    this was a new one for me

    Translation: Password strength: weak. Please don’t use any special characters.

    It was a generated 14 char password… (╯°□°)╯︵ ┻━┻)