edit posts
This commit is contained in:
parent
1189065cde
commit
6ebf324481
22 changed files with 115 additions and 149 deletions
|
@ -1,8 +1,8 @@
|
|||
+++
|
||||
title = 'How Not to Use Cloudflare'
|
||||
date = 2024-04-02T18:20:15+03:00
|
||||
draft = false
|
||||
+++
|
||||
---
|
||||
title: 'How Not to Use Cloudflare'
|
||||
date: 2024-04-02T18:20:15+03:00
|
||||
draft: false
|
||||
---
|
||||
Cloudflare is a DDoS mitigation platform which offers free proxying of your origin server. Unfortunately, this proxying is not well-used by some people, such as the person who inspired me to make this blog post. He has since fixed it. On Sunday, me and a friend of mine have exposed a vulnerability to one of our other friends, which we will be referring for privacy reasons as X. X has agreed to the "hacking" of his website.
|
||||
|
||||
## What is Cloudflare proxying?
|
||||
|
@ -67,4 +67,4 @@ You can mitigate it via numerous ways. Here are the 2 ways you can do that:
|
|||
* Disable Cloudflare proxying: this is the option X chose. This may not be an option for you though if you are subject to frequent (D)DOS attacks.
|
||||
* Deny access of all Cloudflare IPs: there is a handy script on Github made by user Icseon, which uses iptables to deny all non-Cloudflare traffic on port 80 and 443. https://github.com/icseon/cf-iptables
|
||||
|
||||
I hope this blog post has been useful. While I do not use Cloudflare myself, I know many people that do.
|
||||
I hope this blog post has been useful. While I do not use Cloudflare myself, I know many people that do.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue