(04-16-2022, 04:44 AM)mothered Wrote: (04-15-2022, 11:33 PM)Canadian Moose Wrote: Never used a password manager outside of Chrome.
Same here.
In over three decades, I've never had the use for a password manager. I store mine In a text file on an encrypted drive.
I do use a paid password manager/VPN but I barely use the VPN even though it's free. I use a separate VPN to compartmentalize but that's probably not necessary. Solely because I need a password manager to keep my passwords safe, I don't use the actual generator available using the app or desktop/web things. I use this:
Code:
# Generate strong as fuck random passwords using /dev/urandom
# > genpass 70 (or another value)
# Y\vz!b!'nZ4#|E~N$(hV+.TwB/jpZ:1+3*:d47c?`1EK-UC+X7~M1+XB+`A
#
# caveat: generate file name with name "$(genpass 5)"
# $ rm ./\!z\"Wx
# rm: remove regular empty file './!z"Wx'? y
# removed './!z"Wx' make sure you know how to escape \;
#
# useful for things like cloning private repos:
#
# $ read gitadd
# enter https://github.com/git/address.git
# $ git clone $gitadd "$(genpass 6).git"
# Cloning into 'bZ.Nf@.git'...
#
# also considering: LC_CTYPE=C tr -dc '[:print:]' < /dev/urandom | dd bs=35 count=1 2>/dev/null; echo;
genpass ()
{
head -c 500 /dev/urandom | LC_CTYPE=C tr -dc '[:print:]' \
| head -c $1; echo;
}
The part with github is just because I saw a need for cloning git repos for local privilege escalation tools and hiding the repos from the HISTFILE. Yes, you can `export HISTFILE=/dev/null`, but that's meh. I like to automate some level of anti-forensics and I'm a nerd about it, so what?
This may not be viable for other people but it works for me and outputs very strong, secure passwords. It saves me from an actor, exploiting possible browser vulnerabilities, from catching the characters output from the overlay. It's one of the few must-haves for me on all my devices. Your threat model may vary. A password manager is important for many reasons but I'm not shilling them, just stating facts as I know them. The argument is that the RNG within /dev/random and /dev/urandom do not contain true random. But my argument for generating passwords myself is because the entropy within /dev/urandom (PRNG) is efficient to generate characters with high entropy. /dev/random stalls for entropy which can be annoying if you generate keys and it takes 5 minutes to create input. To solve this problem, /dev/random is actually used to create the seed behind the PRNG held within /dev/urandom to save time. Thus, if /dev/random is sufficient enough for key generation (SSH, GnuPG, etc.). I wouldn't use it for personal passwords. But even that would be better than using the pwdgen behind my password manager's code which I can't verify.