Brave browser gets CNAME-based adblocking support - gHacks Tech News

ADVERTISEMENT

Brave browser gets CNAME-based adblocking support

Brave Browser, a Chromium-based web browser that shares its core with Google Chrome, Microsoft Edge, Opera and Vivaldi, will support CNAME-based adblocking in version 1.17 of the browser.

The feature landed in Brave Nightly already and will be integrated in the stable version of the browser in the coming release.

brave-browser-cname based cloaking blocked

Raymond Hill, maker of the popular content blocker uBlock Origin, introduced support for CNAME-based blocking in the Firefox version one year ago. The developer was the first to introduce such functionality in a browser extension, but could do so only in Firefox as Mozilla's browser was, and is, the only browser that supports DNS API capabilities that make such functionality possible in first place.

The Firefox-version of uBlock Origin is therefore the most effective when it comes to content blocking.

Sites and Internet marketing companies may use CNAME cloaking to avoid detection by content blockers, regardless of whether they are integrated in the browser natively, provided by browser extensions, or through other means such as the HOSTS file or DNS.

CNAME tracking, also called CNAME cloaking, works through redirects by using subdomains of the main domain which are then redirected automatically to a tracking domain. Most content blockers distinguish between first and third party resources, and CNAME tracking uses this to avoid detection.

Broken down, the technique makes a resource look like its first party when in fact it is not.

Most browsers cannot detect or block these, and while there are lists, it is necessary to manage the lists manually unless a browser or extension is used that comes with better protection options.

Next to Firefox with uBlock Origin, it is Brave Browser that stepped in. It is the first Chromium-based browser that introduces support for CNAME-based blocking.

Brave Shields, the browser's content blocking solution, will support CNAME-based content blocking in version 1.17 of the browser. The component will "recursively check the canonical name records for any network request that isn't otherwise blocked using an embedded DNS resolver".  The request will then be blocked if it has a CNAME record and if the request would be blocked under the canonical name.

CNAME-based content blocking is enabled by default in Brave 1.17, and it is the first major browser to introduce the functionality as a native solution that is enabled by default.

The company plans to release Brave 1.17 Stable on November 17, 2020 to the public.

Closing Words

Brave is the first browser to provide native on-by-default protection against CNAME-based cloaking techniques. Firefox users who install uBlock Origin are protected as well.

Now You: Have you tried Brave Browser recently?

Summary
Brave browser gets CNAME-based adblocking support
Article Name
Brave browser gets CNAME-based adblocking support
Description
Brave Browser, a Chromium-based web browser that shares its core with Google Chrome, Microsoft Edge, Opera and Vivaldi, will support CNAME-based adblocking in version 1.17 of the browser.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Previous Post: «
Next Post: »

Comments

  1. Anonymous said on November 17, 2020 at 9:15 am
    Reply

    another solution is nextdns, which I use alongside Brave and UbO.

    1. Ray said on November 18, 2020 at 5:41 pm
      Reply

      dnscrypt-proxy can handle this as well.

  2. Akeru said on November 17, 2020 at 9:19 am
    Reply

    Next step for browsers the Google Tag (Server-Side Tagging)… Which has no countermeasure yet.

    1. No Thanks, M$NBCIAGooglesoft said on November 17, 2020 at 10:55 pm
      Reply

      Wait until you hear about Microsoft Pluton. A backdoor into every CPU, with “cloud updates”. That’s right, the CPU will connect to MS servers for updates like a motherboard BIOS. It is a new form of the TPM chip, except now there won’t be any way to disable it if MS has its way.

  3. kirk said on November 17, 2020 at 11:00 am
    Reply

    Would this be rolled out to only Brave for desktop or Brave for Android will get this feature too?

    1. Anonymous said on November 18, 2020 at 3:51 am
      Reply

      well, in github issue they posted tests running on android so it must, especially since desktop and android are the “same”.

  4. BraveBros said on November 17, 2020 at 12:02 pm
    Reply

    CNAME trackers are just another overblown data privacy threat constructed by the fear mongering internet media
    https://old.reddit.com/r/uBlockOrigin/comments/j6zbev/first_party_tracking_list_still_necessary_in/g849ofe/

    1. Anonymous said on November 17, 2020 at 12:34 pm
      Reply

      This problem is similar to the fear mongering about fingerprinting.

      The well-known filterlists included in good content blockers already take care of 100% of all fingerprinting scripts.

      Algorithmic protection is good but since tracking is always javascript-based, all relevant scripts are always added to the filterlists.

      There are only a handful of players in the tracking business, and they are all well-known.

      The biggest privacy problem is server-side tracking when the first-party sends data via their backend. There is not much that can be done against server-side tracking, except regulation by law, which we already have in place in Europe.

  5. Bobo said on November 17, 2020 at 7:14 pm
    Reply

    I like cake.

  6. Anonymous said on November 17, 2020 at 11:42 pm
    Reply

    I don’t have a cnameAliasList.

    ”Change the value of the parameter cnameAliasList to *.”
    https://www.ghacks.net/2019/11/20/ublock-origin-for-firefox-addresses-new-first-party-tracking-method/

    cnameIgnoreList unset
    cnameIgnore1stParty true
    cnameIgnoreExceptions true
    cnameIgnoreRootDocument true
    cnameMaxTTL 120
    cnameReplayFullURL false
    cnameUncloak true
    cnameUncloakProxied false

  7. Anonymous said on November 18, 2020 at 3:26 pm
    Reply

    If the new release can stop the (we see you are using an ad blocker) messages then I would use it.

    1. Pak Pok said on November 18, 2020 at 6:44 pm
      Reply

      well, to be honest, for the way Brave Adblocker works it doesn’t display that message about using an adblocker as much as other extensions, yeah you may say you can install another extension to avoid it more like when Nano Defender existed but I honestly rarely see that message when using native Brave Adblocker only.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.