Retaining AdGuard activation

[The Undertaker]

Retain AdGuard Activation using the whitelisting approach

So you've been using a fix to retain your AdGuard activation and suddenly AdGuard fiddled around with it's settings and your activation gave it's way. The problem is most of the fixes were working on blacklist-approach. Although it works good for the time-being yet it can change any moment at the whims of AdGuard people. So, what works now may not work tomorrow. This is where the whitelist-approach holds an advantage. I'm not saying it's 100% fool-proof but it will survive those little attacks that the blacklist-approach won't be able to handle.

Show Content

Spoiler

• We need to block two domains adguard.com and adtidy.org and allow only what is necessary dependent totally on what the users demand. For illustration purposes, here I'm using Pi-Hole as an example. Here I'm blocking the two domains adguard.com and adtidy.org using wildcards in the Pi-Hole blacklists.
  

Show Content

Spoiler

• Similarly, in the Pi-Hole whitelist, I've provided (exact)exceptions for domains which I need for my use like for downloading filters, extension update, downloading AdGuard setup, accessing their forum, their knowledgebase, etc. This is totally user-dependent.
  

Show Content

Spoiler

And so, my activation retains. You're not bothered by the frequent changes or testing by AdGuard people and your activation should survive for much longer than if you use the blacklist-approach. The same can be applied to AdGuard Home or Acrylic DNS( and maybe DNSCrypt-proxy - not tested).

[The Undertaker]

My Acrylic DNS Proxy rules ( Read this thread on how to add rules) for retaining AdGuard activation:-

Show Content

Screenshot

Code:

0.0.0.0 *.adguard.com
0.0.0.0 *adtidy.org
FW >cdn.adguard.com
FW >filters.adtidy.org
FW >forum.adguard.com
FW >kb.adguard.com
FW >local.adguard.com
FW >sb.adtidy.org
FW >static.adguard.com

Exception Rules explained:-

cdn.adguard.com - For AdGuard extension updation.
filters.adtidy.org - For AdGuard filters updates.
forum.adguard.com - For accessing AdGuard forum.
kb.adguard.com - For accessing the AdGuard knowledgebase.
local.adguard.com - For script injection by AdGuard (cosmetic filtering,etc.)
sb.adtidy.org - For updating browsing security module of AdGuard.
static.adguard.com - For downloading AdGuard setup file and future updates.

[The Undertaker]

Again AdGuard people fiddled with the license check. They now use api-c.adguard.com (and god knows what else) for license check.

And this above mentioned method of whitelisting instead of blacklisting has survived this change and my activation continues to hold strong even now.

[knowledge]

0.0.0.0  api.adguard.com
0.0.0.0  api-b.adguard.com
0.0.0.0  injections.adguard.com
0.0.0.0  sb.adtidy.org
0.0.0.0  filters.adtidy.org



it seems adguard is working on new ways to stop  fixs

think they use 14 now

injections.adguard.com
sb.adtidy.org
filters.adtidy.org
cdn.adguard.com
filters.adtidy.org
forum.adguard.com
kb.adguard.com
sb.adtidy.org
static.adguard.com
api-c.adguard.com
local.adguard.com
api.adguard.com
api-b.adguard.com
ip.api.rec.adguard.com

[The Undertaker]

Here's what mine is showing strictly for license validation :-




As I have said before if you use the whitelist approach as mentioned in this topic your license is safe, but if you depended on the blacklist approach, your activation might have taken a hit. 

Show Content

Spoiler

Everything nice & easy here.

[knowledge]

what adguard is doing to they black list 2 things fontcacheev1from inside C:\ProgramData
and plus they blacklist C:\ProgramData\Adguard
if u remove and start again and block AdguardSvc it can stop them from blocking keys  not sure for how long  as i think soon adguard will start to hit back on fixs and things for its program

i use a patched version but  if i was not patched version 

its best block 0.0.0.0  api.adguard.com
0.0.0.0  api-b.adguard.com
0.0.0.0  injections.adguard.com
0.0.0.0  sb.adtidy.org
0.0.0.0  api-c.adguard.com
0.0.0.0  ip.api.rec.adguard.com

[The Undertaker]

i use a patched version but  if i was not patched version 

its best block
0.0.0.0  injections.adguard.com
0.0.0.0  sb.adtidy.org

I disagree with adding these two domains to block list because they have certain functions :-
sb.adtidy.org - Is for updating the browsing security module.
injections.adguard.com - Is alternative for local.adguard.com when you're using remote injections for script injection & content filtering in AdGuard.

[knowledge]

i use a patched version but  if i was not patched version 

its best block
0.0.0.0  injections.adguard.com
0.0.0.0  sb.adtidy.org

I disagree with adding these two domains to block list because they have certain functions :-
sb.adtidy.org - Is for updating the browsing security module.
injections.adguard.com - Is alternative for local.adguard.com when you're using remote injections for script injection & content filtering in AdGuard.

disagree  is can happen  no problems
injections  can be used against  us the users   something to think about
u maybe right and i maybe wrong but i tested seems fine  but again its options

i did read this sometime ago

Code:

https://forum.adguard.com/index.php?threads/use-localhost-for-injections.28706/

plus i use adguard addon aswell

[The Undertaker]

Code:

0.0.0.0 *.adguard.com
0.0.0.0 *adtidy.org
FW >cdn.adguard.com
FW >filters.adtidy.org
FW >forum.adguard.com
FW >kb.adguard.com
FW >local.adguard.com
FW >sb.adtidy.org
FW >static.adguard.com

Exception Rules explained:-

cdn.adguard.com - For AdGuard extension updation.
filters.adtidy.org - For AdGuard filters updates.
forum.adguard.com - For accessing AdGuard forum.
kb.adguard.com - For accessing the AdGuard knowledgebase.
local.adguard.com - For script injection by AdGuard (cosmetic filtering,etc.)
sb.adtidy.org - For updating browsing security module of AdGuard.
static.adguard.com - For downloading AdGuard setup file and future updates.

An update it seems is required with the new v7. Although the domain is not presently being used for activation purposes but who knows about the future. So, we need to add one more global block rule and a new exception for v7 :-

Code:

0.0.0.0 *adguard.org

Exception for local.adguard.com needs to be removed and a new exception for local.adguard.org needs to be added. All other rules remain the same.

[The Undertaker]

Code:

0.0.0.0 *.adguard.com
0.0.0.0 *adguard.org
0.0.0.0 *adtidy.org
FW >auth.adguard.com
FW >cdn.adguard.com
FW >filters.adtidy.org
FW >forum.adguard.com
FW >kb.adguard.com
FW >local.adguard.org
FW >sb.adtidy.org
FW >static.adguard.com
FW >userscripts.adtidy.org

Updated the list with latest domains that need to be blocked/whitelisted for v7.