Hacker News new | past | comments | ask | show | jobs | submit login

> Yes, if you cut the search space arbitrarily by something like 110 bits or so, the math works differently. So? That's not the game.

See- the search space is already significantly under 256-110 bits.

The search space is a bit smaller than 92 bits in passwordle. If it drew uniformly from the possible characters it would be 92 bits; it's more like 87-88 bits since it does not draw uniformly.

This is out of reach of brute force--- as I've said the entire time-- but if it were just a few characters shorter it would be within reach. 11 is doable with a lot of computing; 9 would be trivially doable. They chose 14 characters of input.

This is an interesting offline-online tradeoff. 10 guesses doesn't get you far vs. a 9 character random password in practice. But 10 guesses with this oracle lets you defeat 9 character random passwords easily. (and provides enough information to defeat 14 character random passwords, but with no feasible search strategy known at this time).

This is very different from "provides no information whatsoever". I suspect you not appreciating this is why we have a difference of opinion.

> Your strategy completely depends on having a list of precomputed hashes for the entire search space.

It depends upon being able to do a meaningful amount of search offline-- either precomputed or before your last guess.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: