Cloudflare: Difference between revisions

From Soyjak Wiki, The Free Soycyclopedia
Jump to navigationJump to search
No edit summary
Tag: Reverted
No edit summary
Tag: Reverted
Line 1: Line 1:


A website is also re-purposed to serve propaganda like ''"Verifying security..."'' and ''"Did you know every third person you meet is actually a botnet under a coat?"'' if the website owner resorts to those full-page Cloudflare captcha checks. The goal is to make it appear justified to deny access to most websites VPN and TOR users, objectors to Javascript and generally those who run a functioning web browser but don't conform to however way Cloudflare intends to track you, which puts in cause an openness principle of the World Wide Web, while you believe the connection protection is for your protection.
= The Man in the middle =
Cloudflare-protected servers are instanced across a vast [https://en.wikipedia.org/wiki/Content_delivery_network content-delivery-network], with visitors never interacting with the real server. The unencrypted contents of user's interaction are entirely handled by Cloudflare.
{{quoting|
For a site to use cloudflare, the owner has to point their DNS records to cloudflare's servers, at which point they effectively handed cloudflare full control of their website (as long as the DNS records point to cloudflare's servers). ...
For a site to use cloudflare, the owner has to point their DNS records to cloudflare's servers, at which point they effectively handed cloudflare full control of their website (as long as the DNS records point to cloudflare's servers). ...
However, this is not a [https://en.wikipedia.org/wiki/Man-in-the-middle_attack Man-in-the-Middle attack], because the website owner gave cloudflare permission to do all of this. So it's not an attack, it's a secure connection to cloudflare (who the website owner gave permission to serve content at their domain name).
However, this is not a [https://en.wikipedia.org/wiki/Man-in-the-middle_attack Man-in-the-Middle attack], because the website owner gave cloudflare permission to do all of this. So it's not an attack, it's a secure connection to cloudflare (who the website owner gave permission to serve content at their domain name).

Revision as of 14:25, 5 August 2023

For a site to use cloudflare, the owner has to point their DNS records to cloudflare's servers, at which point they effectively handed cloudflare full control of their website (as long as the DNS records point to cloudflare's servers). ... However, this is not a Man-in-the-Middle attack, because the website owner gave cloudflare permission to do all of this. So it's not an attack, it's a secure connection to cloudflare (who the website owner gave permission to serve content at their domain name). |"dr jimbob" — Information Security Stack Exchange }} This is functionally a man-in-the-middle attack, but it's passively accepted as a fact of using the internet at this point. From hosting your bank's website to soyjak.party, Crimeflare dominates the CDN market with an 80% share, essentially performing a man-in-the-middle-attack on all of the internet. Some have pointed out the colossal datamining potential of such a position, but the argument loses ground when verified fact-checkers revealed the proponents are dangerous, unmedicated conspiracy theorists.


See also

On soyjak.party

Soot enabled Cloudflare in an attempt to stop Colorjak, CP and other types of spam. At first it was accepted, even with some users starting to defend the decision, calling all the Cloudflare detractors as spammers but it quickly became an annoyance to most users as cloudflare requires you to refresh the page every five minutes. Higher protection modes also block archive sites from taking snapshots.

oh yeah and cloudflare makes it so i can't access the website right now this is retarded kuzzy

Citations