I guess I'm almost to the next level (Legendary) except I was randomly chosen to wait a little bit longer.
As was I.
I feel robbed.
Seems there are a few of us on the verge of becoming legend
. @DH, we both even have the same activity
.
Re: the secretSeed, the resulting hash is substr'ed to extract only two hex digits, so if I'm not mistaken there are tons of seeds that yield the same substr(sha1(…), 1, 2). It's easily bruteforceable.
The substr is done
after the hashing. If the
secretSeed were
substred before the hashing, then you're right that the
secretSeed (or rather, the relevant byte of the secret seed) could be brute-forced given enough data. Unfortunately, the way it is set up right now, the entire state space for the
secretSeed must be brute-forced to retrieve it (or a vulnerability in SHA1 found).
You are correct that there are many seeds that yield the same hash, for
one particular user id. However, if you have data for that one particular user id, there is no point brute-forcing anyways.