Earlier quoted context omitted.
About the benchmark data: It looks like your pow_sha256 library is using is the "sha2" crate, which is a pure Rust implementation of SHA2. So your benchmark is around the delta of your library compiled to native code vs. your library compiled to WASM, which is an interesting benchmark but I don't think it answers the right question. A more interesting benchmark would probably answer the question "what would those loo…
That's a good idea, I'll be sure to do that!
mCaptcha – Proof of work based, privacy respecting CAPTCHA system
31–40 of 100 posts
Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#32Just checked a commercial captcha solving service, Recaptcha rate is currently at $1-$2 per thousand. Looks like this is only going to be cheaper to operate commercially.
Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#33Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#34This fights spammers, that use own server, but this will not protect from hostile taken computers, that can use their hash power to resolve the captcha.
Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#35Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#36I couldn‘t figure out how this scheme works - the only detail I found is that there is „a bunch of maths“ and replay protection of some sort. Is there a technical protocol description somewhere? I‘d be interested in reading this.
1. mCaptcha sends a PoW configuration(first XHR request in the demo widget[0]) which includes a challenge text("string"), a salt and a difficulty factor
2. Client generates proof of work by concatenating "string" + salt until difficulty factor is met. If difficulty factor isn't satisfied, it will continue trying to generate Proof of Work(PoW) by appending nonce and incrementing it until the difficulty factor is satisfied.
3. Client sends PoW to mCaptcha, which includes nonce, original salt and "string"(second XHR request in the demo widget)
4.mCaptcha computes hash for "string" + salt + nonce. If difficulty factor is met(i.e resultant hash > difficulty factor), then mCaptcha responds with access token.
5. Client sends access token to the web service.
6. Web services authenticates access token with mCaptcha and only grants access to protected resource, if the token checks out.
I will work on a more detailed specification and report back when it is ready(3 weeks, I think)
[0]: https://demo.mcaptcha.org/widget/?sitekey=pHy0AktWyOKuxZDzFf...
disclosure: author of mCaptcha
Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#37Did I miss something or is that description not sufficiently crypto-y enough?
Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#38The goal of CAPTCHA is to tell computers and humans apart. I appreciate the effort towards better UX, but there are already "invisible" CAPTCHAs like Botpoison that discriminate better than this. PoW solutions are just more energy-intensive rate limits.
Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#39Also the idea ain’t so new!: http://www.hashcash.org/hashcash.pdf
Re: mCaptcha – Proof of work based, privacy respecting CAPTCHA system
#40Earlier quoted context omitted.
That's a good idea, I'll be sure to do that!
Also remember that native code can use multithreading, so if your challenge is something that could be farmed out to multiple CPU threads until one finds the solution, that's another factor in favor of native code performance.
If all it takes is computer time, then that's a cheap thing for the botnet operator to solve. They can just spin up another instance, and split up the crawling task to another computer (or 200).