owsei

joined 1 year ago
[–] [email protected] 8 points 3 weeks ago

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

[–] [email protected] 2 points 3 weeks ago (1 children)

Damm, I legit didn't knew there bcrypt had a length limit! Thank you for another reason not to use bcrypt

[–] [email protected] 27 points 3 weeks ago

Also rate of the requests. A normal user isn't sending a 1 MiB password every second

[–] [email protected] 20 points 3 weeks ago (15 children)

Why are you hasing in the browser?

Also, what hashing algorithm would break with large input?

[–] [email protected] 89 points 3 weeks ago (24 children)

The problem is that you (hopefully) hash the passwords, so they all end up with the same length.

[–] [email protected] 5 points 4 weeks ago

A day before I got in a guy set fire to the trash in the chapel. So I befriended him immediately!

[–] [email protected] 3 points 2 months ago

Thank you very much!

[–] [email protected] 8 points 2 months ago (2 children)

Is there an index of the images or something like that?

[–] [email protected] 25 points 2 months ago (2 children)

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%

[–] [email protected] 12 points 4 months ago (2 children)

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.

[–] [email protected] 1 points 4 months ago

thank you very much

 
view more: next ›