• LordKitsuna@lemmy.world
    link
    fedilink
    arrow-up
    16
    ·
    4 days ago

    I like testing websites maximum length. I’ll set bitwarden random generator to like 100 and see if it accepts the password. After that I start testing if it’s actually using the whole password or arbitrarily cutting it off early without telling me

    • deo@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      17
      ·
      4 days ago

      i have totally run into stuff that silently truncates the password i give it. It’s always something like online banking that you would hope has robust enough security standards to hash that shit, too… The one in particular i’m thinking of silently truncated the password in the reset-password form, but not for the log-in form. Took me forever to figure out wtf was going on there.

      • undefined@links.hackliberty.org
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        2 days ago

        Banks are still doing SMS-based 2FA. And after doing some security training at work written by the FBI and seeing it suggest switching letters/numbers around to make a password “more secure” (like th15); I’ve completely lost confidence in banks’ security standards.

      • jet@hackertalks.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 days ago

        Banks are world class leaders in technical inertia. Almost certainly at some point when they’re designing their system they’ve got a interface from the 1970s or maybe even the 1980s if it’s a new bank, that has to work with everything else which has the limited input fields. And that just propagates to all the other systems in these weird ways

        Oh yeah we’re using a file system that integrates over LDAT but it only looks at the first eight characters cuz the rest are used for the domain etc etc etc