• laurelraven@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    55
    arrow-down
    2
    ·
    3 months ago

    That’s only really true if you’re going to be storing the password in a secure vault after randomly generating it; otherwise, it’s terrible because 1) nobody will be able to remember it so they’ll be writing it down, and 2) it’ll be such a pain to type that people will find ways to circumvent it at every possible turn

    Pass phrases, even when taken with the idea that it’s a limited character set that follows a semi predictable flow, if you look at it in terms of the number of words possible it actually is decently secure, especially if the words used are random and not meaningful to the user. Even limiting yourself to the 1000 most common words in the English language and using 4 words, that’s one trillion possible combinations without even accounting for modifying capitalisation, adding a symbol or three, including a short number at the end…

    And even with that base set, even if a computer could theoretically try all trillion possibilities quickly, it’ll make a ton of noise, get throttled, and likely lock the account out long before it has a chance to try even the tiniest fraction of them

    Your way is theoretically more secure, but practically only works for machines or with secure password storage. If it’s something a human needs to remember and type themselves, phrases of random words is much more viable and much more likely to be used in a secure fashion.

    • hedgehog@ttrpg.network
      link
      fedilink
      arrow-up
      11
      ·
      3 months ago

      Generally people don’t memorize private keys, but this is applicable when generating pass phrases to protect private keys that are stored locally.

      Leaving this here in case anyone wants to use this method: https://www.eff.org/dice

        • hedgehog@ttrpg.network
          link
          fedilink
          arrow-up
          2
          ·
          3 months ago

          Thanks for that! I recommend anyone who wants to minimize risk to follow their instructions for self-hosting:

          Is the source code available and can I run my own copy locally?

          Yes! The source code is available on Github. Its a simple static HTML application and you can clone and run it by opening the index.html file in your browser. When run locally it should work when your computer is completely offline. The latest commits in the git repository are signed with my public code signing key.

    • bjorney@lemmy.ca
      link
      fedilink
      arrow-up
      5
      ·
      3 months ago

      We are talking about RSA though, so there is a fixed character length and it isn’t meant to be remembered because your private key is stored on disk.

      Yes the word method is better than a random character password when length is unbounded, but creating secure and memorable passwords is a bit of an oxymoron in today’s date and age - if you are relying on remembering your passwords that likely means you are reusing at least some of them, which is arguably one of the worst things you can do.

    • Fetus@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      3 months ago

      Most of my passwords are based around strings of characters that are comfortable to type, then committing them to muscle memory. There’s a few downsides to this:

      • If I need to log in to something on mobile and don’t have a proper keyboard with me, it’s tough to remember which symbols I’ve used

      • I share some of my logins with friends and family for certain things, if they call and need to re-enter a password, it’s usually impossible to recite it to them over the phone (most of my shared logins have reverted back to proper words and numbers to make it easier for the others)

      • If I lose an arm, I’ll probably have to reset all of my passwords.

      But yeah, words alone provide plenty of possibilities. There’s a reason cryptocurrency wallets use them for seed phrases.

    • ClamDrinker@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      3 months ago

      And even with that base set, even if a computer could theoretically try all trillion possibilities quickly, it’ll make a ton of noise, get throttled, and likely lock the account out long before it has a chance to try even the tiniest fraction of them

      One small correction - this just isn’t how the vast majority of password cracking happens. You’ll most likely get throttled before you try 5 password and banned before you get to try 50. And it’s extremely traceable what you’re trying to do. Most cracking happens after a data breach, where the cracker has unrestricted local access to (hopefully) encrypted and salted password hashes.

      People just often re-use their password or even forget to change it after a breach. That’s where these leaked passwords get their value if you can decrypt them. So really, this is a non-factor. But the rest stands.

      • laurelraven@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        2
        ·
        3 months ago

        That’s fair

        It’s still a rather large pool to crack through even without adding more than the 1000 most common words, extra digits, minimal character substitution, capitalization tweaks, etc