3 ms·

Yikes! I see this too: <script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e1781791509496 https://st

Yikes! I see this too: <script type="module" src="https://static.cloudflareinsights.com/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e1781791509496 https://static.cloudflareinsights.com/beacon.min.js/v4513226..." integrity="sha512-ZE9pZaUXND66v380QUtch/5sE9tPFh2zg45pR2PB0CVkCtOREv2AJKkSidISWkysEuQ0EH8faUU5du78bx87UQ==" data-cf-beacon='{"version":"2024.11.0","token":"c0859b51a7804ab5a9cc8e9e2b2c4cde","r":1}' crossorigin="anonymous"></script>

kevincox 2mo ago
Yup, I explicitly had all anaytics turned off. But had a few sites using Cloudflare for caching. Now I'm checking and seeing this on all of them. This is gross and unacceptable. "Caching" does not mean "modifying my site".
- zx8080 2mo ago
  MITM attack, that's what it is. Why is this not in the news? Ah, no one cares.
  - reaperducer 2mo ago
    Why is this not in the news? Good point. There should be a place where hackers can get this kind of news. Some kind of Hacker News place.
  - zeafoamrun 2mo ago
    It takes a lot of trust to let a CDN be able to terminate TLS traffic for you and this doesn't exactly give the warm fuzzies.
  - ironmagma 2mo ago
    Cloudflare is essentially MITM as a service. What else would someone expect?
- chrisweekly 2mo ago
  Adding a RUM beacon for observability / performance metrics capture, as an opt-out feature for free plans (opt-in for paid plans), is not exactly nefarious. Hopefully/presumably there was some communication before the change was rolled out.
  - matherial 2mo ago
    No. I was on a free plan for years and found out by accident. It's interesting that you set "nefarious" as the bar. I'd simply call it "sleazy".
stackghost 2mo ago
I'm not seeing this on my site (if you want to check: https://stackgho.st https://stackgho.st), are you using their `strict` http settings? I.e. is your server terminating TLS or is theirs? edit: perhaps it's only for sites added after that policy came into effect

kevincox 2mo ago

Yup, I explicitly had all anaytics turned off. But had a few sites using Cloudflare for caching. Now I'm checking and seeing this on all of them. This is gross and unacceptable. "Caching" does not mean "modifying my site".

zx8080 2mo ago
MITM attack, that's what it is. Why is this not in the news? Ah, no one cares.
- reaperducer 2mo ago
  Why is this not in the news? Good point. There should be a place where hackers can get this kind of news. Some kind of Hacker News place.
- zeafoamrun 2mo ago
  It takes a lot of trust to let a CDN be able to terminate TLS traffic for you and this doesn't exactly give the warm fuzzies.
- ironmagma 2mo ago
  Cloudflare is essentially MITM as a service. What else would someone expect?
chrisweekly 2mo ago
Adding a RUM beacon for observability / performance metrics capture, as an opt-out feature for free plans (opt-in for paid plans), is not exactly nefarious. Hopefully/presumably there was some communication before the change was rolled out.
- matherial 2mo ago
  No. I was on a free plan for years and found out by accident. It's interesting that you set "nefarious" as the bar. I'd simply call it "sleazy".

stackghost 2mo ago

I'm not seeing this on my site (if you want to check: https://stackgho.st https://stackgho.st), are you using their `strict` http settings? I.e. is your server terminating TLS or is theirs? edit: perhaps it's only for sites added after that policy came into effect