First time I've seen a visualisation before solve :D
I took one look at pt2 and noped out, its a later problem I think...
I think we basically did the same bug, but I did it in rust.
160ms is respectable, I am at 300ms. Probably should remove my sqrt.
I think they are on different scales, there is no bruteforcing involved in https/SSL.
Its usually designed so that you can't rainbow table.
give me a string that starts with "xyz", and hashes to "000..."
That can't be rainbow tabled, as the server can force a different salt.
(Note, I dont know the exact algorithms involved, just the general theory)
Yeah, max of 256 paths, and if there were no holes in the splitter layout, it would be the full 256. Also why i had to limit the depth to 16 layers, more than that and the brute forcing gets a bit silly.
Day 8: https://youtu.be/QiezRG4jiUM
Getting pretty close to having written my own game renderer, only slower and worse :D
And once free, the idiot tries to pick a fight again....
Proof of work means that your client has to do some "work" in order to gain access. It typically means a challenge that can't be trivially solved, but can be trivially verified.
For example, the challenge may be something to the effect of:
"Give me a string, that when hashed by md5, results in a hash that ends in 1234".
Your browser can then start bruteforcing until it finds a string (should take a few seconds max), and then it can pass the string back to the server. The server can verify with a single hash, and you're in.
Its not wildly different to crypto mining, but the difficulty is much lower for antibot, as it needs to be solveable in seconds by even low end devices.
Thats cool! What are the colours meant to signify?
That is a very unoptimal pt2 time! Have you tried profiling to see what's causing the slowdown? Mine is 300ms, or worst case, 4s to process all links.
Ha, love an excel solution, please do share it in the solutions thread!