Lolint: > Hi > > One of the possible solutions that was mentioned earlier concerning Cloudflare captchas was generation .onion automatically for sites on Cloudflare to make things easier all round. However Cloudflare's CEO didn't want such solution because "weak hash used by .onion means theoretical risk you can create collision on two addresses." [https://twitter.com/eastdakota/status/710357574579650560 > ](https://twitter.com/eastdakota/status/710357574579650560) > Now that coming next-gen onion services will use stronger crypto that would eradicate the problem above, does that mean that we will finally see a workaround to Cloudflare's captchas? I don't think so as I don't see how next generation .onion services solve the underlying problem. Georg
Attachment:
signature.asc
Description: OpenPGP digital signature
-- tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk