What is the sense of permiting the user to use no passwords longer than xx chars?

Its more like a usability question or maybe database, or even maybe security (consider injection attacks) but what is the sense of permiting the user's password to a be not longer than xx chars? It does not make any sense to me, because longer passwords are mostly considered better and even harder to crack, and some users use password safes, so the password length should not matter.

I understand that passwords with more than 20 chars are hardly to remember, but if you use diceware or password safe you dont have any problem with that. I really cant understand why there are sites that say "your password need to be between 5 and 8 chars"...

also should the password saved as hash, so the length of the field in the database is fixed, so where is the problem?

i think that most of the sites where the password is has to be a fixed length are not even using any hashing method...


Whenever you see an upper limit for your choice of a password, you can guess that they want to store it un-hashed. And that's really bad.

Passwords are 'the longer the better' and they should also be composed of letters from an alphabet as big as possible. The differences are quite well explained here: https://www.grc.com/haystack.htm

Need Your Help

How do I use functionality available in an embedded jar file?

jar xamarin monodroid

I'm trying to use GmailSender in my Xamarin Android app. My main project is referencing the binding library, and the binding library has 2 jars - GmailSender 1.1.jar, and mail.jar.

Duck type as syntactic sugar for reflection: Good or bad idea?

refactoring language-design syntactic-sugar duck-typing

I've been thinking lately, would it be a good form of syntactic sugar in languages like Java and C#, to include a "duck" type as a method parameter type? This would look as follows: