1485
this post was submitted on 05 Jul 2023
1485 points (98.4% liked)
Android
28000 readers
201 users here now
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I totally understand. I think you're missing my point.
I am willing to bet multiple sites we both signed up store their passwords in cleartext (or unsalted hashes, or broken hashing methods).
So the attackers now have one of our passwords. They may even have a number of our passwords. In my case, using a password manager, the attacker has multiple completely random strings that I have used as passwords. In your case, the attacker has 2 passwords that look very much the same, although a little changed. You are now screwed.
Then you should know that attackers don't take your plain-text or cracked password and the start manually guessing similar codes on your other accounts, unless they are exactly the same. They always need to get a copy of your password (we'll assume its hashed), then start the guess work using a decoder.
How secure your password is to the program depend on its entropy, which depends on the password's length and possible characters. Two passwords are either exactly the same or completely different, and not how similar it "looks" to human.
Now, obviously if you make a easy-to-guess scramble (e.g. password123 becomes password123facebook for, well, facebook) then the hacker can do a custom decoder and this does compromise security. There are a lot of little tricks to avoid this, in anycase it will be secure as long as you maintain a high entropy.
Oh they absolutely do.
You keep going back to hashing methodology. I totally agree that if the website hashes your password correctly, its unlikely to be compromised.
That said, you are trusting the website in that regard, when it has been repeatedly proven that there are sites, even large ones, have exposed passwords.
You said at the beginning of this thread that you can't trust password managers to manage your password correctly. But you trust random websites with that password instead.
So put your hashing discussion to one side, and think of the scenerio where your passwords are not encrypted. Because you can't guarentee that they are.
What got me into this discussion was your comment
It is just such bad advice. Anyone who thinks changing a few letters in their password used accross multiple sites deserves to be hacked.
Edit: I'm going to stop here. I don't think I'm getting through. Thanks for the chat.
I’ll just finish off with a few more points
If your password is unencrypted or poorly encrypted, having a random string vs custom password makes no difference. The whole point of unique and strong password is so that a poorly encrypted service does not compromise your properly encrypted service. The scenario where my password is unencrypted is irrelevant, because only the salted hashed password matters. And because of the hash, leaking unencrypted passwords does not make the hashed ones easier to guess.
The whole issue with a manager isn’t that its bad, its that it puts everything under the one basket, even if its a hella strong basket. If you want to change my mind, you need to show the pros outweigh the cons. Straight up assuming that not using a manager somehow means anytime I have my password compromised equals everything else is compromised is not convincing, its circular reasoning.
Ignoring the fact that I’m explaining how hash works and not giving advice, if we want to be technical then yes only a slight change does make targeted attack easier. At that point password will only provide so much security, if you want to truely be safe, grade separate your username and email.
Thanks for the chat too, have a nice day
Edit: grammar