From d6ccae24bb5cf2105a367145058f333be60cf63a Mon Sep 17 00:00:00 2001 From: Raymond Hill Date: Sun, 26 Nov 2017 09:40:59 -0500 Subject: [PATCH] Updated How to work only with global rules and all scripts blocked by default (markdown) --- ...only-with-global-rules-and-all-scripts-blocked-by-default.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md b/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md index 862094a..1f97a05 100644 --- a/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md +++ b/How-to-work-only-with-global-rules-and-all-scripts-blocked-by-default.md @@ -4,7 +4,7 @@ The motivation for this article is the following argument made at Wilders Securi The way you work your ruleset with uMatrix is not dictated by uMatrix. If you want to work strictly with global rules, i.e. rules that apply everywhere, uMatrix allows that. -Using an example page, this is uMatrix with out-of-the-box ruleset: +Using an example page, this is uMatrix with out-of-the-box ruleset -- by default uMatrix is set up to work with per-base domain rules: ![a](https://user-images.githubusercontent.com/585534/33240862-77db100a-d28b-11e7-8e51-416ea0e5cafb.png)