• @[email protected]
    link
    fedilink
    27
    edit-2
    14 hours ago

    Why the password.trim()? Silently removing parts of the password can lead to dangerous bugs and tells me the developer didn’t peoperly consider how to sanitize input.

    I remember once my password for a particular organization had a space at the end. I could log in to all LDAP-connected applications, except for one that would insist my password was wrong. A trim() or similar was likely the culprit.

    • @[email protected]
      link
      fedilink
      1012 hours ago

      The reason for leaving in the password.trim() would be one of the few things that I would ever document with a comment.

    • @[email protected]
      link
      fedilink
      2414 hours ago

      Another favorite of mine is truncating the password to a certain length w/o informing the user.

      • @[email protected]
        link
        fedilink
        English
        1010 hours ago

        Saving the password truncates but validation doesn’t. So it just fails every time you try to log in with no explanation. The number of times I have seen this in a production website is too damn high.

          • @[email protected]
            link
            fedilink
            English
            16 hours ago

            Passwords should be hashed, not stored plain text! Hashes are always the same length so this is an immediate sign they are doing horribly insecure things with your password.

      • @[email protected]
        link
        fedilink
        512 hours ago

        The password needs to be 8 letters long and may only contain the alphabet. Also we don’t tell you this requirement or tell you that setting the password went wrong. We just lock you out.

    • @[email protected]OP
      link
      fedilink
      11
      edit-2
      14 hours ago

      Thanks for the tip. password.trim() can indeed be problematic. I just removed that line.