Strongly disagree. I don’t trust anyone with my passwords, especially since they are all vulnerable. LastPass was just recently hacked and it could happen to any of the other services as well. It may sound insane, but internalizing your passwords is going to always be the most secure. I came up with a simple algorithm I use to help remember my passwords, all sites are associated with a 6 letter shortcode, and I have a way to convert that into a secure password that is 12 characters of mostly random alphanumerics and symbols. Sure, it’s not something that everyone would want to do, but your sentiment of “not whether or not, but which one” is not correct for everyone.
internalizing your passwords is going to always be the most secure. I came up with a simple algorithm I use to help remember my passwords
Every pattern, no matter how clever, reduces entropy and makes your passwords less secure than a randomly generated one.
I agree with you about the cloud services though. I would never trust the most sensitive data to an online service. They have to be competent to stay in business but they’re guarding a real treasure there.
From my understanding, none of the last pass master passwords or saved passwords were identified or taken though - they still kept the passwords secure despite hackers accessing files…
You could use Himitsu and sync your passwords across devices with Syncthing, instead of encouraging people to confuse security with pedantry. Cybersecurity measures should be as transparent as possible, and nowadays cumbersome solutions also tend to be insecure. See, for example, pass(1): totally not secure, and also cumbersome to use. Compare that with SSH, developed by the OpenBSD project: it just works, especially by delegating complexity, i.e. by letting users and admins set up another secure channel, via HTTPS, to drop the SSH key.
The OpenBSD project has also developed doas, signify, libtls, scp, which are all no-brainers. Mastering doas is literally one blog post away.
Strongly disagree. I don’t trust anyone with my passwords, especially since they are all vulnerable. LastPass was just recently hacked and it could happen to any of the other services as well. It may sound insane, but internalizing your passwords is going to always be the most secure. I came up with a simple algorithm I use to help remember my passwords, all sites are associated with a 6 letter shortcode, and I have a way to convert that into a secure password that is 12 characters of mostly random alphanumerics and symbols. Sure, it’s not something that everyone would want to do, but your sentiment of “not whether or not, but which one” is not correct for everyone.
Every pattern, no matter how clever, reduces entropy and makes your passwords less secure than a randomly generated one.
I agree with you about the cloud services though. I would never trust the most sensitive data to an online service. They have to be competent to stay in business but they’re guarding a real treasure there.
From my understanding, none of the last pass master passwords or saved passwords were identified or taken though - they still kept the passwords secure despite hackers accessing files…
You could use Himitsu and sync your passwords across devices with Syncthing, instead of encouraging people to confuse security with pedantry. Cybersecurity measures should be as transparent as possible, and nowadays cumbersome solutions also tend to be insecure. See, for example, pass(1): totally not secure, and also cumbersome to use. Compare that with SSH, developed by the OpenBSD project: it just works, especially by delegating complexity, i.e. by letting users and admins set up another secure channel, via HTTPS, to drop the SSH key.
The OpenBSD project has also developed doas, signify, libtls, scp, which are all no-brainers. Mastering doas is literally one blog post away.