👨💻 Professional problem solver - 🎧 Music lover
Hello! Thanks for checking out my profile.
If you haven't yet, make sure to also follow me on my other social media! ⬇️
👨💻 Professional problem solver - 🎧 Music lover
Hello! Thanks for checking out my profile.
If you haven't yet, make sure to also follow me on my other social media! ⬇️
Tbh, the length of a password is the only strength indication. And should be the only criteria you'd enforce.
You'd have a better user experience and strong passwords.
It doesn't matter if a password has a unique character or not. As long as you allow for them then a potential brute forcer has to include them in their tests.
Bringing AI & machine learning right to where you are in your workflow. Supercharging tools like GitHub, VS Code, JetBrains, Browsers, and more! Try Pieces for Developers Suite for free today!
switch (score) {
case 0:
case 1:
case 2:
return "Weak";
case 3:
return "Medium";
case 4:
return "Fine";
case 5:
return "Strong";
default:
return "extra strong";
}
We're a place where coders share, stay up-to-date and grow their careers.
A "strong" password:
Löl1Indeed, Löl1 is very strong.
Yeah, except that it's not.

I was just joking bro. :-)
Tbh, the length of a password is the only strength indication. And should be the only criteria you'd enforce.
You'd have a better user experience and strong passwords.
It doesn't matter if a password has a unique character or not. As long as you allow for them then a potential brute forcer has to include them in their tests.
The password pattern I used in the post is generally accepted in the development community.
What I built is an indicator not forcing the user to go one or another way.
Great share!
Thank You!
Great read.
Glad you liked it.
Really interesting post , good job
Thanks for your kind words.
It works fine in my case:
switch (score) {case 0:
case 1:
case 2:
return "Weak";
case 3:
return "Medium";
case 4:
return "Fine";
case 5:
return "Strong";
default:
return "extra strong";
}