Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, toxicity and dog-whistling are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either !asklemmyafterdark@lemmy.world or !asklemmynsfw@lemmynsfw.com.
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email info@lemmy.world. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try !politicaldiscussion@lemmy.world or !askusa@discuss.online
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Strong passwords aren't intended to simply protect against brute-forcing a password via trying to authenticate repeatedly, but also to help protect against brute-force attempts to obtain passwords from a compromised password database using a dictionary attack, the scenario you're describing.
Typically
if an authentication system is storing its password database competently
the password shouldn't be stored in plain text. Instead, the password will be salted (to avoid rainbow table attacks) and then hashed via a cryptographic hash. The password database entry will look something like a tuple of (username, salt, salted hashed password). If the password is a strong one, it will be computationally-hard to obtain the plaintext password, even if someone has the salt and the salted, hashed password.
I know using a strong password is important, but thats the bare minimum. this is more directed to the people who think strong passwords are the grail and will LITERALLY not do anything else, and call people paranoid schizos when they try to suggest security
That's fair.
What would you have them do? What are they missing?
Yeh, for 99% of casual internet users... they just aren't going to care about that.
They don't want their email/Facebook/back account pwnd.
Like, at all.
It's like saying that 0.01% of traffic fatalities are because an airbag forces your head into the roof of the car. So you should wear a helmet when driving.
You aren't wrong.
Internet is a massive part of our daily lives. We should be able to fully trust the things we use to interact with it.
But convenience is going to win