Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Friday March 05 2021, @09:38PM   Printer-friendly

AdGuard names 6,000+ web trackers that use CNAME chicanery: Feel free to feed them into your browser's filter:

AdGuard on Thursday published a list of more than 6,000 CNAME-based trackers so they can be incorporated into content-blocking filters.

CNAME tracking is a way to configure DNS records to erase the distinction between code and assets from a publisher's (first-party) domain and tracking scripts on that site that call a server on an advertiser's (third-party) domain. Such domain cloaking – obscuring who controls a domain – undoes privacy defenses, like the blocking of third-party cookies, by making third-party assets look like they're associated with the first-party domain.

[...] The most commonly detected CNAME trackers, according to the researchers, come from the following companies, in order of prevalence: Pardot, Adobe Experience Cloud, Act-On Software, Oracle Eloqua, Eulerian, Webtrekk, Ingenious Technologies, TraceDock, LiveIntent, AT Internet, Criteo, Keyade, and Wizaly.

[...] "In order to prevent it you'll need to use a content blocker that can access DNS queries," Andrey Meshkov, CEO of AdGuard, told The Register.

"The whole problem is that the majority of users don't use them and just stick to Chrome or Safari browsers with extensions. These users can only 'react' to the problem, they can only start blocking a new disguised tracker as soon as we detect it on AdGuard DNS and update the list."

Meshkov acknowledged that this is not a proactive approach, but it works within the existing system for applying filtering lists to content blockers.

[Ed Note: I use and can recommend Pi-hole for your home network. That doesn't help though when you're on the road unless you VPN back to your home network first. - Fnord]


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by black6host on Saturday March 06 2021, @04:46AM (2 children)

    by black6host (3827) on Saturday March 06 2021, @04:46AM (#1120697) Journal

    From the per-requisite section of the documentation:

    As part of our install process, we append some lines to /etc/dhcpcd.conf in order to statically assign an IP address, so take note of this before installing.

    Anyone know if this behavior can be changed easily? I've already got my pi set up with a static IP and I am running it headless. I really don't want to change any of that...

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Saturday March 06 2021, @01:59PM (1 child)

    by Anonymous Coward on Saturday March 06 2021, @01:59PM (#1120770)

    It will prompt you to keep current settings or change them during install.
    If you're just getting started my pro-tip is that you will also have to masquerade all dns traffic through the pihole. You'll be amazed at how much shit uses hard-coded DNS servers to get around DNS ad blocking.

    • (Score: 0) by Anonymous Coward on Sunday March 07 2021, @11:00AM

      by Anonymous Coward on Sunday March 07 2021, @11:00AM (#1121019)

      I just block it at my firewall. You don't play nice, I don't play nice.