aeris22’s avataraeris22’s Twitter Archive—№ 76,867

  1. …in reply to @Paul_Reviews
    @Paul_Reviews @CanterRain So you have to compute X hashes for each fudge during the login. Good hash algorithm is asic resilient, and **must** hash in not less than 200ms per hash. 10 fudges tested = 2s of latency. Or you have to do parallel matching with threads, which is *really* over engineered…
    On twitter.com Twitter logo aeris22’s avatar Mood +3 🙂
    1. …in reply to @aeris22
      @Paul_Reviews @CanterRain And if you thread your matching, you facilitate bruteforcing, because each bruteforcing try tests really for X passwords…
      Permalink On twitter.com Twitter logo aeris22’s avatar Mood 0