• ragebutt@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    5
    ·
    18 days ago

    Why not local

    Like just generate an md5 hash, truncate it to whatever arbitrary number the shitty website decided is their password length limit, then store it in an encrypted db

    Of course this is just a long way of reinventing keepass/1password/bitwarden/icloud keychain/etc

      • toynbee@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        18 days ago

        I haven’t in a while, but back when I generated passwords for users, I would use the openssl command.

      • ragebutt@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        18 days ago

        An md5 of whatever string pops in your head at that moment. True randomness is a persons nonsequitors

        This makes sense. I had no idea what tools existed because as mentioned many db solutions exist for this