6 ms·
Just leave it at passwordpassword, it will be leaked eventually anyway Strong passwords that need to be memorized shouldn't be wasted on security bozos
by raverbashing 10y ago
Just leave it at passwordpassword, it will be leaked eventually anyway
Strong passwords that need to be memorized shouldn't be wasted on security bozos
- contravariant 10y agoI can kind of understand that reasoning, but one of the nicer things about strong passwords is that there are a lot of them. In some sense that's what makes them strong passwords.
- rovr138 10y agoHe doesn't need to memorize it. He mentioned he used 1Password to generate it. I'd assume he's storing it there too.
- raverbashing 10y agoAt the very least you need to memorize the 1pw password, but I do memorize some others as well
- _ao789 10y agoI've always wondered when 1Password is going to get hacked..
- oddevan 10y agoWon't do much; AFAIK everything is encrypted client-side with your master password. So a hacker could, in theory, get my encrypted database, but by the time they crack my strong password, I will, at the very least, have changed all those passwords.
- developer2 10y agoThat's not what a hack against 1Password, LastPass, or similar product will look like. When it happens, it will be because someone manages to commit to the VCS repository of one or more of their client applications (iOS, Android, desktop, etc.). All it takes is a few lines of code to dump the unencrypted contents on the device itself, and post them to some API endpoint or email address. One commit to a VCS by a disgruntled employee, or an attacker who social engineers credentials to the VCS, and the client applications themselves - which must be trusted to decrypt the contents locally - will be compromised. This is the problem with proprietary password managers, where the client applications are provided by the company. You cannot vet that software which is running on your device today, let alone all the app updates coming down the pipeline.
- SnacksOnAPlane 10y agoThank you for writing this. I use a password manager, and whenever I see someone say "it's unhackable because of the encryption" I want to tell them this, exactly. All someone needs to do is to surreptitiously send your password to their own server and all your passwords are owned. It's not difficult.
- hcurtiss 10y agoI've often wondered about this. Is there a preferable alternative?
- Buge 10y agoWhy do you assume the password would be leaked eventually? Usually hashes are leaked (as in this case), not passwords.
- throwaway729 10y agoleaking unsalted md5 passwords == leaking passwords
- Buge 10y agoNot if it's my password. I use ~100 bits of entropy.
- supergreg 10y agoCould the attacker find an easier to find string that matches the same md5 hash?
- Dylan16807 10y agoThe current best attack wrt matching an existing hash brings MD5's 128 bits of security down to 123. So no, that's not going to happen.
- throwaway729 10y agoHence "Strong passwords that need to be memorized" in OP's comment. Or else your memory is way better than mine (or I care way less, or probably both).
- Buge 10y agoWhether they need to be memorized or not does not make the statement "it will be leaked eventually anyway" more true. I use a password database so I don't memorize most of my passwords.
- 10y ago