network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 9 months |
| seen | Apr 4 at 18:20 | |
| stats | profile views | 2 |
|
Aug 6 |
awarded | Scholar |
|
Aug 6 |
awarded | Supporter |
|
Aug 6 |
comment |
How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry? It will not be stored anywhere in the database. The password becomes: itself+salt (and saved by user.) |
|
Aug 6 |
comment |
How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry? See edit at the bottom of my question. Thanks for making me realize that wasn't clear. |
|
Aug 6 |
awarded | Editor |
|
Aug 6 |
revised |
How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry? added 58 characters in body |
|
Aug 6 |
comment |
How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry? a) Thanks. b) "The purpose of a salt is not to make computing the hash slower" - True, but it is to make the number of possibilities larger, and so to create the table (or search for a possibility that will give that hash) - will take longer. 100M/s is slow compared to the 2^400 possibilities in the case I outlined. |
|
Aug 6 |
awarded | Student |
|
Aug 6 |
asked | How many possibilities can today's computers check (per second) in a SHA512 hash of a 50-byte-long random entry? |
