>>223518

>>223513

To add to this: Its a way one hash.

password: superQ

ends up looking something like this: 0e81794384491161f1777c12fad6a93f8146f337a69a25e73043362938b9824

in the database. Only way to crack is to keep guessing the exact password or the exact salt above (from a list of associated passwords to hash tables), not by reverse engineering the random salt above.

Not happening in the time frame for this project.

Hashfags feel to correct anything I've posted.

>>223723

>you mean something like….

Its possible.

>>223844

>Whatever, we have all that we need. Q told us that.

and a lot of it is being erased in the older threads on a daily basis.