It's going to have to be site-specific code to by-pass different implementations however. And it still means that the attacker has to write something to interpret what the hoster is sending and expects back. It would probably be easier just to throw a javascript interpreter into their code.
Eh. They already have to write implementation-specific code.
It's more about proving that you took the cpu cycles to do it. Unfortunately, the server must have to do the exact same work to compare answers!
I'm mistaken on that last part.
http://en.wikipedia.org/wiki/Hashcash#Sender.27s_side It takes a long time for the sender to calculate but is quick and easy for the receiver to verify.
Previous Topic
Index
