How many websites can handle the amount of traffic that CF can handle? It’s not just about configuring your firewall, it’s about having the bandwidth. Otherwise it’s not much of a DDoS protection.
That’s what I’ve been saying throughout this thread. The only significant DDoS protection offered by Cloudflare requires CF seeing the traffic (and holding the keys) so it can treat the high-volume traffic. If CF cannot see the payloads, it cannot process it other than to pass it all through to the original host (thus defeating the DDoS protection purpose).
As I don’t have an account there I can’t see which requests containing credentials use which cert.
Why would you need an account? Why wouldn’t bogus creds take the same path?
If it’s true that this is unverifiable, that’s good cause to avoid Cloudflared banks. It’s a bad idea for customers to rely on blind trust. Customers need to know who the creds are shared with /before/ they make use of them -- ideally even before they make the effort of opening an account.
And also, just because the cert is verified by cloudflare does not mean they have the private key.
This uncertainty is indeed good cause to avoid using a Cloudflared bank.
UPDATE: I’ve spoken to some others on this who assert that it is impossible for a bank customer to know for certain if a bank uses their own key to prevent disclosure to CF.
Some of these take an ethical step backwards. I see the pattern: lemmy.ml on the left-hand side, which is generally a good idea because lemmy.ml is centralized by disproportionate numbers. But when you have another quite large node on the RHS which is rendered strictly centralized by Cloudflare, you have a downgrade. E.g. the nodes lemmy.ca and lemmy.one should appear on the LHS, and for transparency I suggest tagging them with a lightening cloud (🌩).