Damm, I legit didn't knew there bcrypt had a length limit! Thank you for another reason not to use bcrypt
owsei
Also rate of the requests. A normal user isn't sending a 1 MiB password every second
Why are you hasing in the browser?
Also, what hashing algorithm would break with large input?
The problem is that you (hopefully) hash the passwords, so they all end up with the same length.
A day before I got in a guy set fire to the trash in the chapel. So I befriended him immediately!
Thank you very much!
Is there an index of the images or something like that?
While it's true that's a progess bar is guessing (since it doesn't know what would take more time in your computer). It should still finish when at 100%
Even if they do have the same in-memory representation, you may want to assert types as different just by name.
AccountID: u64
TransactionID: u64
have the same in-memory representation, but are not interchangeable.
thank you very much
I'd say 128 is understandable, but something like 256 or higher should be the limit. 64, however, is already bellow my default in bitwarden