I’m aware of what constitutes a decent password, but typing in 15-30 random characters each time I lock my computer screen is starting to get a bit taxing.

How secure does my user password really need to be and what are the threats to it? Does the same apply to a root-enabled user as a “regular” user when it comes to password security?

For context, my threat model doesn’t need to account for real people breaking in and accessing my computer, the damage would be very contained.

Bonus question - what are the risks of having a weak password on a root user on a spare laptop on the same network as my main device that is used exclusively for web browsing? Thanks.

  • communism@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    3 months ago

    For context, my threat model doesn’t need to account for real people breaking in and accessing my computer, the damage would be very contained.

    I mean if you don’t have open ssh ports on your computer or whatever I don’t think you need a strong password, given that you’re not concerned about physical access. I would say that at the very least have a reasonably secure root password (/user password if you’re a sudoer/anyone else who can get root permissions with your user account) because if you end up with some malware on your computer that can, say, enter passwords, you don’t want it to be ridiculously easy to bruteforce.

  • stoy@lemmy.zip
    link
    fedilink
    arrow-up
    4
    ·
    3 months ago

    Using random characters is dumb.

    It incetivices you to write it down (which in and of itself isn’t a completely terrible idea).

    As an IT guy, let me tell you, STOP using random passwords!

    Use passphrases instead, it is far easier to remember a sentence than a random string of letters and numbers.

    • Caveman@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      3 months ago

      “nobody can crack this password in a million years” in pretty strong

      Edit :

      “nobody can crack this password in a million years with current technology”

    • SentientFishbowl@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Agreed - the message I was trying to convey is that I use a very secure password, which sacrifices convenience for security - is this necessary though? I have no concerns related to memorising or particular difficulties typing it out as it follows a passphrase structure for the most part.

    • Random Dent@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Yeah that’s my preferred method too. Bitwarden’s password generator can create passphrases too, so I have it just create random ones for pretty much everything. The only ones I have to remember are the ones to unlock Bitwarden itself, and the one to unlock the decryption when I boot my PC up. So like two sentences essentially. I literally don’t even know what the passwords are to anything else lol.

    • astrsk@fedia.io
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      One can also mix in numbers and symbols and capital letters with their passphrase / sentence. Throw in a comma, exclamation mark, replace an l with 1, o with 0, etc. of course it’s diminishing returns with a sufficiently long passphrase but it can help against dictionary type attacks by adding additional mutations / steps to the cracking.

      • IphtashuFitz@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 months ago

        Years ago I worked at a company where they based server root/admin passwords on song lyrics. The person who came up with it clearly liked classic rock. I still remember at least one of them:

        4ThoseAboutToRockWeSaluteYou!

        • astrsk@fedia.io
          link
          fedilink
          arrow-up
          1
          ·
          3 months ago

          Lyrics are a pretty good base. Especially in passphrase style with spaces if supported, along with punctuation and capitals/numbers. What sucks is when an account system can’t support a long password. That’s the most frustrating requirement for any service and the greatest vulnerability of all the common restrictions.

    • otp@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      3 months ago

      I was wondering why 1 year was in the red category, but then I realized that that time could decrease quite a bit over time with technological advances

      EDIT: typo

      • golli@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        3 months ago

        The chart also doesn’t specify what hardware the calculation is based on. If it’s “1 year to crack for your average desktop PC”, then a server farm will do so in minutes.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      The hash doesn’t matter from a device perspective. The OS enforces a retry delay and a person would need to use a keyboard.

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

      This is for random characters but “interestingpassword” will get cracked by a dictionary attack almost instantly.

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

    Physical security is more important than software security on laptops. In a public space it’s enough to have a shit password as long as there is one.

    For ssh ports or remote desktop connections that don’t use pairing you definitely need a strong password. For local WIFI connections it’s not as important as your WIFI security though.

  • youmaynotknow@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    I use a pretty simple password in my PC and Laptop, since, in theory, I’m the only one with access to them (oh, and my wife, of course).

    I just don’t have ssh enabled and the root passwords are ridiculously strong.