deCloudflare/deCloudflare
deCloudflare/deCloudflare
0
0
Fork 0
mirror of https://git.sdf.org/deCloudflare/deCloudflare/ synced 2024-06-08 23:20:48 +00:00
Code Issues Releases Activity

change instances of MITM to MiTM - #8

Browse Source
This commit is contained in:
Amolith 2019-05-24 08:32:59 -04:00
parent 67fff2f34e
commit d425d2cd53
No known key found for this signature in database
GPG Key ID: 51FD40936DB0065B
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
article.txt
View File

@ -79,8 +79,8 @@ More important, though is it starts to form a ratchet for web browser technology
"When you fetch a page from a website that is served from Cloudflare, Javascript has been injected on-the-fly into that page by Cloudflare. And they also plant a cookie that brands your browser with a globally-unique ID. ID. This happens even if the website is using SSL and shows a cute little padlock in your browser" [10]
- Cloudflare tracks you
Even if your web browsing traffic is protected from onlookers, Cloudflare itself because they are a MITM[14][31] can see your traffic[6].
And if Cloudflare[53] has attacked your traffic(MITM), then so has the NSA[33].
Even if your web browsing traffic is protected from onlookers, Cloudflare itself because they are a MiTM[14][31] can see your traffic[6].
And if Cloudflare[53] has attacked your traffic(MiTM), then so has the NSA[33].
"If a site uses Cloudflare, then the browser lock icon is a false promise."[14]
"The short version, a rhetorical question: Would you trust a key escrow regime, in which an “authorized” entity was entrusted with the potential to decrypt all communications at will? If not, why would you trust a de facto mass decryption chokepoint at which many communications are actually decrypted?"[34]
in other words
@ -219,7 +219,7 @@ as a consequence:
*Cloudflare DNS*
"DNS[50] is around, servers are insecure, proper end-to-end crypto isn't the norm hence MITM goes unnoticed, anonymity is an edge case, routing lacks built-in resiliency to disruption, we're always going to have actors building a bus.ness model around cobbling together superficial, overapproximating mitigations."[20]
"DNS[50] is around, servers are insecure, proper end-to-end crypto isn't the norm hence MiTM goes unnoticed, anonymity is an edge case, routing lacks built-in resiliency to disruption, we're always going to have actors building a bus.ness model around cobbling together superficial, overapproximating mitigations."[20]
*Mozilla and Cloudflare*