PLEASE help test Lemmy 0.18 fixes, enterprise.lemmy.ml is the testing server with latest code
PLEASE help test Lemmy 0.18 fixes, enterprise.lemmy.ml is the testing server with latest code
This next version is quite important as it brings important fixes.
Bugs: https://enterprise.lemmy.ml/c/actualbugs018
cross-posted from: https://sh.itjust.works/post/300197
Enterprise: enterprise.lemmy.ml - Thank you!
I notice a few UI-related things:
(Still need to test pinned messages being moved when sorted by new) (I should post this in there, actually, I guess)
Is there a reason you consider passwords longer than 60 characters an issue, or does the backend reject such passwords? In my experience, there should be no upper bound on password length except maybe in the order of request size being too large (say a password that is a several kilobytes).
The 60 character limit is not a problem imo, the problem is that they are truncated at 60 but the UI doesn't tell you, this results in some problems.
Some password encryption methods has max characters length. For example Bcrypt has 72 max length. This is mostly to avoid taking too much time encrypting user input.
If there's no limit someone can technically froze the server by inputting large password (not because the request is big, but encryption process is exponentially takes more CPU process the longer it is)
Passwords "should" be hashed anyway, so I don't understand why there's a limit. Are they actually being stored as plaintext in a VARCHAR(60) column in the database? Please tell me that's not happening.
Is it possible if you can submit that comment as a post in enterprise.lemmy.ml cause that way the devs could see your thoughts? Or you could submit it as a ticket in the issues tab in lemmy-ui I guess if that's more convient