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…
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.
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.
deleted by creator
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…
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.
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.