(Still remember: if they have a password length limit, they store the password in plain text! If they do that in the backend. They can do that in the frontend too, in the browser with javascript, which is safe.)
Why would you say that? Services are able to require special characters, variable casing and numbers. Why would the reqirement of max length of the password cause the storage to succumb to plain text?
He should have said a short length limit, it’s still recommended to have a length limit of some sort (I think 64 is the official recommendation) to prevent people from doing shit like pasting the entire Shrek script as a password (because you KNOW some people will lol)
Max. 16 characters
(Still remember: if they have a password length limit, they store the password in plain text! If they do that in the backend. They can do that in the frontend too, in the browser with javascript, which is safe.)
Why would you say that? Services are able to require special characters, variable casing and numbers. Why would the reqirement of max length of the password cause the storage to succumb to plain text?
This simply depends on if they do that in the browser with Javascript (good) or on the backend.
So yes, the statement that I copied from someone else is not always true.
Lemmy-UI has a password limit of 60 characters. Does that mean they are storing your password in plain text?
I think they could also check that length with Javascript in the browser. Dont know, you should ask the devs.
You are right and that’s exactly what happens in your 16 char example.
He should have said a short length limit, it’s still recommended to have a length limit of some sort (I think 64 is the official recommendation) to prevent people from doing shit like pasting the entire Shrek script as a password (because you KNOW some people will lol)
No, that means they don’t like DoS attacks.
Does anyone like being on a receiving end of those?