Re:We didn't encrypt your password, we hashed it
by gbear605 on Friday September 04, 2020 @08:22PM
(#24380312)
Some passwords are too long - I wouldn’t expect any website to accept a gigabyte long password - and I wouldn’t judge a site that doesn’t accepts \0 either.
[ Parent
| on HN ]
Re:We didn't encrypt your password, we hashed it
by tdrp on Friday September 04, 2020 @08:37PM
(#24380412)
I don't remember the math on hashing/bcrypt but isn't this the case that all passwords sort of hash to a fixed length string? Like why even have something like "your bank password must be 8-12 characters" long.
Obviously for a gigabyte long it's a bandwidth and hash-computing issue :p
Re:We didn't encrypt your password, we hashed it
by masklinn on Saturday September 05, 2020 @02:43AM
(#24381788)
> Obviously for a gigabyte long it's a bandwidth and hash-computing issue :p
Yes, that’s why you put in limits which are way beyond reasonable passwords but way below that. Say a few hundred or thousand bytes.
Also worth consideration: most of these work on bytes, probably utf8. A user wants to be cute and put emoji in there, that’s 4 bytes a pop. So depending how the system counts them, “hospital plane” might be considered 2, 4 or 8 characters.
But wait! Group emoji are concatenation combinations thereof, you can have a single multi-character emoji which is composed of half a dozen codepoints, and two dozen bytes once encoded.
Re:We didn't encrypt your password, we hashed it
by couchand on Friday September 04, 2020 @11:16PM
(#24381154)
bcrypt's input is limited to 72 characters in most implementations.
https://cheatsheetseries.owasp.org/cheatsheets/Password_Stor...