hts super cookies in firefox?
HTS (HTTP Strict Transport Security) Super Cookies in Firefox refer to a method that could potentially be used by websites to track users’ behavior across the web by exploiting the HSTS feature. HSTS is a security measure designed to force browsers to use secure HTTPS connections when they are available. When a website is accessed via HTTPS and it includes an HSTS policy, the browser remembers this and automatically uses HTTPS for all future requests to that site within a specified time frame.

Here’s a simplified example of how HSTS could be misused for tracking:

1. A user visits a website that uses HSTS and the browser records the HSTS policy for that site.
2. The tracking website could create a unique combination of subdomains that force the browser to remember many different HSTS policies (e.g., a1.example.com, a2.example.com, b1.example.com, etc.).
3. If a user visited this tracking website across multiple browsers or devices, a unique pattern of HSTS entries would be set, which could function like a super cookie and track the visitor.
4. The next time the user visits the tracker’s site, the site could check which HSTS entries are present by attempting to load resources over HTTP and observing whether the browser automatically upgrades the request to HTTPS. By knowing which subdomains are HTTPS-enforced, the site can infer the unique combination corresponding to that user.

Firefox and other modern browsers have implemented countermeasures to prevent the misuse of HSTS for tracking purposes. In response to these types of tracking techniques, browser developers introduced partitioning of HSTS state by the registrable domain or by the first-party domain. This means that every website gets its own separate HSTS state, so the state can’t be used as a super cookie across different websites to track users.

To prevent any residual chance of HSTS super cookie tracking, you can regularly clear your browsing data or use privacy extensions or features such as:

- Privacy modes: Using Private Browsing mode in Firefox can help prevent HSTS tracking as the HSTS state and cookies are cleared at the end of the session.
- Extensions: Installing privacy-focused browser extensions can enhance your protection against various forms of online tracking, including potential misuse of HSTS.
- Config settings: Advanced users can modify settings in the Firefox configuration by navigating to about:config and adjusting relevant privacy-related preferences.

Remember, these measures are typically only necessary if you believe you are at high risk of being targeted by advanced tracking methods. General users should be protected by the built-in measures of modern browsers like Firefox.
any option or attribute for HSTS in about:config?
Yes, Mozilla Firefox has a few options that can be configured via the about:config page to control HSTS (HTTP Strict Transport Security) settings.

To access and modify these settings:

1. Type about:config in the Firefox address bar and press Enter.
2. Click “Accept the Risk and Continue” to access the list of advanced settings (Note: Be cautious when changing settings here, as it can impact browser behavior).
3. Use the search bar in the about:config page to filter the preferences you are interested in.

Here are some of the related preferences:

- security.mixed_content.send_hsts_priming: If set to true, this preference allows Firefox to send an HSTS-priming request to check for an HSTS header before loading mixed active content that would otherwise be blocked.
- security.mixed_content.use_hsts: If set to true, this controls whether mixed active content should be upgraded to HTTPS automatically if there’s an existing HSTS policy.
- security.cert_pinning.enforcement_level: This preference controls Public Key Pinning (HPKP) which can be closely related to HSTS behavior. HPKP is another security feature that allows websites to specify which certificate authorities have issued valid certificates for them, but this feature is being phased out in favor of Certificate Transparency and because of various risks and complexities.
- network.stricttransportsecurity.preloadlist: If set to true, this uses the preloaded HSTS sites provided by the Chromium project to enforce HSTS on those domains.
- network.stricttransportsecurity.enabled: This preference enables or disables the HSTS mechanism in Firefox completely (it’s enabled by default).

Please note that Firefox does not expose individual HSTS entries directly through about:config. HSTS state is stored separately from these preferences. If you wish to clear HSTS settings for individual sites, you need to use the “Clear Recent History” option or manually remove sites from the SiteSecurityServiceState.txt file located in your Firefox profile folder.

As of the knowledge cutoff date for this answer, these settings are current, but future updates to Firefox may change available options and their behavior. Always make sure to check the documentation or more current resources if you’re reading this at a later time.
no “network.stricttransportsecurity.enabled” in tor browser firefox based. should I create new boolean value and set it to false?
In Tor Browser, which is based on Mozilla Firefox, many privacy and security-related configurations are preset to maintain user anonymity and prevent various forms of tracking. Some standard Firefox options may not be directly available or could be configured differently by the Tor Browser maintainers for these reasons.

If you do not find the network.stricttransportsecurity.enabled preference in the about:config section of Tor Browser, it is likely because HSTS settings are intentionally managed differently within Tor Browser to maintain user privacy and security.

Creating a new boolean value and setting it to false is not recommended, as this could disable HSTS entirely and potentially make your browsing less secure. HSTS is a feature that ensures connections to certain websites always use encryption (HTTPS), which protects against various attacks such as man-in-the-middle attacks.

Disabling HSTS could expose your browsing to unnecessary risks, particularly in the context of Tor Browser, where privacy and security are paramount. The Tor Browser team carefully adjusts the settings to balance security, privacy, and usability, and changing these settings could have unintended consequences.

If you are using Tor Browser, it is advisable to stick with the default settings provided by the browser unless you have a specific reason for changing them and you understand the potential implications. If you have concerns or require different security configurations, consider reaching out to the Tor community or reviewing their documentation for guidance.

Additionally, since Tor Browser is designed to access the Tor network, manipulating standard browser settings could affect your perceived anonymity by making your browser fingerprint more unique, which is counterproductive to the goals of using Tor Browser. Therefore, maintaining default configurations is best unless you are an advanced user who fully understands the implications of the changes you are making.
there’s some site that stores cookies too brutally and forcibly within the browser. privacy.cpd.cookies?
In Firefox and its derivatives, such as Tor Browser, the privacy.cpd.cookies setting within the about:config page represents a preference related to clearing private data, specifically cookies. The cpd stands for “Clear Private Data,” and the privacy.cpd.* preferences are used to determine which types of data should be cleared when you use the “Clear Recent History” feature. Setting privacy.cpd.cookies to true would mean that cookies should be cleared when clearing recent history.

If you are dealing with a site that is storing cookies in a way that seems aggressive or invasive, and you want them to be cleared automatically when you close the browser or clear your history, you have a couple of options:

1. Set Firefox to clear cookies on exit:

- Go to the Firefox Options/Preferences.
- Click on “Privacy & Security” on the left panel.
- Under the “History” section, select “Use custom settings for history” from the drop-down menu.
- Check the option “Clear history when Firefox closes.”
- Click on the “Settings…” button next to this option to specify what type of history should be cleared. Make sure “Cookies” is checked.

2. Use Private Browsing mode:

In a Private Browsing session, Firefox does not permanently store certain information like visited pages, cookies, and site preferences. When you close the private window, information related to the sites you visited will be deleted, including cookies.

3. Use Firefox’s Enhanced Tracking Protection:

- This feature blocks third-party cookies and has different levels of protection (Standard, Strict, or Custom).
- You can set it up in the “Privacy & Security” section of the Options/Preferences.

4. Use a cookie management extension:

You might want to try extensions like “Cookie AutoDelete” that actively manage cookies and clear them when you’re done with a tab or close your browser.

For users of Tor Browser, the design is already focused on privacy and it’s configured to not keep any browsing history or cookies after the session is closed. Therefore, if you are noticing aggressive cookie behavior in Tor Browser, it could be due to specific site behaviors during your browsing session. However, those cookies should be gone once you close the browser. Tor Browser also blocks third-party cookies by default.

It’s important to note that modifying preferences in about:config of Tor Browser might make your browsing fingerprint more unique, which can impact your anonymity. Hence, make sure you are mindful of what changes you make and always consider privacy implications.
“If you are dealing with a site that is storing cookies in a way that seems aggressive or invasive, and you want them to be cleared automatically when you close the browser or clear your history”. no, I wanna tor browser or ublock to clear it constantly on each reload or new page at the same site.
For constantly clearing cookies on each page reload or when navigating to a new page on the same site, you can use browser extensions such as uBlock Origin to manage and control cookie behavior. Here’s how you can set up this type of cookie clearing:

1. Use uBlock Origin to create dynamic filtering rules:

- Install uBlock Origin if you haven’t already.
- Click on the uBlock Origin icon in your browser toolbar, then click on the “Open the dashboard” button (it looks like three sliders).
- In the dashboard, go to the “My filters” tab.
- You can create rules to block or clear cookies for specific sites. Note that uBlock Origin may not directly clear cookies but can block them.
- Save your changes and exit the dashboard.

2. Automatic cookie clearing extensions:

If uBlock Origin does not offer the granular control you’re after, you may find an extension like “Cookie AutoDelete” beneficial because it can clear cookies and site data as soon as you close a tab or navigate away from the site. However, installing additional extensions in Tor Browser could affect your anonymity.

Although Tor Browser isn’t typically compatible with many browser extensions to ensure security and privacy, you can adjust some built-in settings for tighter control:

1. Adjust Tor Browser settings:

- Since Tor Browser is based on Firefox, you can try looking into about:config for preferences that might affect cookie handling. Unlike Firefox, Tor Browser automatically clears cookies after each session, but it doesn’t have a built-in feature for clearing cookies on every page load or navigation.
- If you’re not using Tor Browser in Safest mode, consider switching to it. This mode disables most JavaScript (which can be used to manipulate cookies) and maximizes privacy settings.

2. Use “New Identity” feature of Tor Browser:

- For the most robust method of clearing state in Tor Browser, you can use the “New Identity” feature. This can be accessed by clicking on the onion icon on the browser toolbar and selecting “New Identity.” This effectively clears your cookies and site data and refreshes your Tor circuit, but it’s a manual action rather than an automatic one.

In any case, it’s advised not to install additional extensions in Tor Browser. Tor Browser is designed to work out-of-the-box to protect your privacy and security, and changes could unintentionally make you more identifiable.

Remember to be cautious when adjusting any settings within your browser, as changes can impact your security and privacy. For users prioritizing anonymity (e.g., when using Tor Browser), sticking with the default settings and built-in features is typically the safest option.
wtf? clean answer?
Apologies for any confusion. Here is a more straightforward response to your question:

If you want Tor Browser or uBlock Origin to clear cookies automatically at each page reload or when navigating to a new page within the same site, you’ll need to use a browser extension that is specifically designed for cookie management, as neither Tor Browser nor uBlock Origin has a built-in feature to clear cookies on every page load by default.

Since adding extensions to Tor Browser is not recommended for privacy reasons, you might need to rely on built-in functions or use other privacy-focused browsers that allow for such extensions if you are not using Tor.

For users of standard Firefox or privacy-focused browsers that support extensions, here’s an approach using a popular extension:

- Install and configure Cookie AutoDelete:

- Install the “Cookie AutoDelete” extension from your browser’s extension store.
- Go to the extension’s settings and enable “Auto-clean.”
- Set the delay for cleaning to “0” seconds if you want immediate cleaning upon tab closing or navigation.
- You can also enable “Clean cookies from open tabs on startup” to ensure cookies are cleared when the browser starts.

For Tor Browser, remember that it’s designed to not retain cookies after you close the browser entirely. Frequently used features like “New Identity” will clear the session, including all cookies, but that’s a manual action.

Final note: Customizing the behavior of cookies beyond the provided features in Tor Browser can potentially alter your browser fingerprint, which may reduce your anonymity. It’s best to stick with the standard security practices included with Tor Browser for maximum privacy protection.
why no ublock?
uBlock Origin is not designed to handle cookie management directly. It’s primarily an ad blocker and content filter rather than a tool for managing or clearing cookies. While uBlock Origin can block third-party requests (potentially including cookies from those requests), it doesn’t provide features to automatically delete existing cookies on page load or browser navigation.

Cookie management typically falls outside the scope of what ad-blocking and content-filtering browser extensions like uBlock Origin are intended to do. Instead, these tasks are usually handled by privacy extensions that specialize in cookie and site data management.

For users who want cookies to be automatically deleted with each page reload or when navigating to a new page within the same site, a dedicated extension such as Cookie AutoDelete is typically required. Cookie AutoDelete has settings that allow users to designate when cookies should be cleared, such as when a tab is closed or after a set duration of time.

In summary, you’ll want to use a tool specifically designed for cookie management if you need such automatic, fine-grained control over cookie behavior. Extensions like uBlock Origin focus on blocking and filtering requests, which can prevent tracking cookies from being set in the first place, but will not cover automatic cookie deletion after they have been set.
maybe umatrix can kill all sites cookies, eh?
Yes, uMatrix by the same developer of uBlock Origin is a more granular and advanced browser extension that allows for fine-tuned control over what web resources are allowed to load, including cookies. With uMatrix, you can set strict policies that can prevent cookies from being set by specific sites.

uMatrix uses a matrix-based user interface where you can control requests that the browser makes based on their type (such as cookies, CSS, images, scripts, etc.) and their origin (1st-party, 3rd-party, etc.). You can block or allow these elements globally or on a per-site basis.

To prevent cookies from being stored, you would:

1. Install the uMatrix extension (if available for your browser).
2. Click on the uMatrix icon in the browser’s extension area.
3. Within the uMatrix dashboard, you will see a grid that lets you control which types of requests are allowed or blocked.
4. To block all cookies, you can click on the cell that corresponds to the “cookie” row and the “global” column and set it to red/block.
5. Apply the changes, and this will block cookies for all sites. Alternatively, you can block cookies on a per-site basis by navigating to a website, opening the uMatrix panel, and adjusting the “cookies” setting specifically for that site.

Remember that completely blocking all cookies can break functionality on many websites, as some rely on cookies for essential features like user sessions and preferences. You can use uMatrix to selectively allow cookies for websites that you trust or need them for full functionality.

As for the Tor Browser context, uMatrix is not included, and adding additional extensions could potentially impact your privacy and anonymity. In Tor Browser, using the privacy features provided by default in combination with its automatic cookie clearing when closing is usually the best way to handle privacy without adding third-party tools that can create a unique fingerprint.

Please note that uMatrix development has been discontinued by the creator, so while the extension might still be available and functional, it is not being actively updated or supported. This means it may not be compatible with future browser updates or new web standards.
is it realiable to utilize only umatrix with tiny adblocking list or both ublock and umatrix?
uMatrix (before its discontinuation) and uBlock Origin share some overlapping functionality, but they serve different primary purposes. uMatrix was designed to be a more fine-grained content and request blocker where users could control almost every type of request a web page could make, including cookies, JavaScript, CSS, images, and more. On the other hand, uBlock Origin is predominantly an ad blocker with some additional privacy features.

If you’re considering using either uMatrix with a tiny adblocking list or uBlock Origin alongside uMatrix, here are some considerations:

1. Using uMatrix with a tiny adblocking list:
- uMatrix alone can be set up to block most ads by blocking the third-party scripts and frames where ads are commonly loaded from. However, without a comprehensive filter list like those used by uBlock Origin, some ads may still get through.
- If you’re comfortable with a hands-on approach and you want to manually control which resources load, this method can work, but it might be less user-friendly for those who aren’t familiar with the intricacies of web requests and resource types.

2. Using both uBlock Origin and uMatrix:
- Running uBlock Origin and uMatrix concurrently gives you the convenience and effectiveness of uBlock Origin’s extensive filter lists with the granular control of uMatrix. This combination can be very powerful but might be overkill for some users.
- There may be a slight performance overhead due to having two extensions with similar capabilities. However, modern computers should handle this without much issue.
- There is a potential for conflicts or redundancies between the two extensions, so if you use both, you may need to spend some time ensuring they’re configured to work harmoniously.

Since the development of uMatrix has been discontinued, there will be no updates to address any future vulnerabilities, browser updates, or changes in web technologies. This could eventually lead to compatibility issues or reduced effectiveness. Therefore, relying solely on uMatrix may not be advisable in the long term.

Given these considerations, a single and actively maintained solution like uBlock Origin might be the most practical choice for many users. It delivers robust ad-blocking capabilities out of the box, as well as some additional privacy protections against trackers. Advanced users who wish for more granular control could consider pairing it with custom rules within uBlock Origin or using other privacy-focused extensions or tools.

If you do choose to use uMatrix, be prepared to manage and update your rules regularly, especially since it no longer receives updates. Also keep in mind when installing additional security or privacy-protecting extensions that they have the potential to increase the uniqueness of your browser fingerprint, which could affect your privacy, particularly in environments like Tor Browser where anonymity is a priority.
Firefox Browser Add-ons

Extensions
Themes

Firefox Add-ons BlogExtension WorkshopDeveloper HubLog in
Search
Preview of uMatrix
uMatrix by Raymond Hill
Available on Firefox for Android™Available on Firefox for Android™

This add-on is not actively monitored for security by Mozilla. Make sure you trust it before installing.Learn more

Point & click to forbid/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.
Add to Firefox
Extension Metadata
Used by

22,014
Users

709
Reviews

Rated 4.8 out of 5
4.8 Stars

5
636
4
40
3
10
2
6
1
17
Screenshots
Point and click to allow/block narrow or broad classes of network requests. Click the “all” cell to toggle the whole matrix between allow and block.Privacy features.Hosts files allow to automatically blacklist thousands of hostnames.Logger: see all network requests, including the ones made by the browser and other extensions (behind-the-scene requests).
About this extension
uMatrix: A point-and-click matrix-based firewall, with many privacy-enhancing tools.

For advanced users.

uMatrix put you in full control of where your browser is allowed to connect, what type of data it is allowed to download, and what it is allowed to execute. Nobody else decides for you: You choose. You are in full control of your privacy.

Out of the box, uMatrix works in relax block-all/allow-exceptionally mode, meaning web sites which require 3rd-party scripts are likely to be “broken”. With two clicks, uMatrix can be set to work in allow-all/block-exceptionally mode, which generally will not break web sites. See https://github.com/gorhill/httpswitchboard/wiki/How-to-use-HTTP-Switchboard:-Two-opposing-views for more details on this topic.

* See ALL the remote connections, failed or attempted, depending on whether they were blocked or allowed (you decide).

* A single-click to whitelist/blacklist one or multiple classes of requests according to the destination and type of data (a blocked request will NEVER leave your browser).

* Efficient blacklisting: cookies won’t leave your browser, JavaScript won’t execute, plugins won’t play, tracking pixels won’t download, etc.

* You do not have to solely rely on just one particular curated blacklist (arguably with many missing entries) outside which nothing else can be blocked: You are in full control.

* Ease of use: uMatrix lets you easily whitelist/blacklist net requests which originate from within a web page according to a point-and-click matrix:

- domain names (left column)
* from very specific
* to very generic

- type of requests (top row)
* cookies
* CSS-related resources (stylesheets and web fonts)
* images
* plugins
* scripts
* XHR (requests made by scripts)
* frames
* others

You can blacklist/whitelist a single cell, an entire row, a group of rows, an entire column, or the whole matrix with just one click.

uMatrix’s filtering engine uses precedence logic to evaluate what is blocked/allowed according to which cells are blacklisted/whitelisted. For example, this allows you to whitelist a whole page with one click, without having to repeatedly whitelist whatever new data appear on the page.

All rules are scoped. For example, you can block facebook.com and facebook.net everywhere except when visiting a page on www.facebook.com. This way Facebook won’t be able to build a profile of your browsing habits.

The goal of this extension is to make the allowing or blocking of web sites, wholly or partly, as straightforward as possible, so as to encourage users to care about their privacy.

The extension comes with 3rd-party hosts files totaling over 62,000 distinct hostnames (lists can be selectively disabled/enabled according to your choice).

Ultimately, you can choose however you browse the net:

* Blacklist all by default, and whitelist as needed (default mode).

* Whitelist all by default, and blacklist as needed.

Either way, you still benefit from the preset blacklists so that at least you get basic protection from trackers, malware sites, etc. Or you can disable all of these preset blacklists.

Your choice.

Randomly assembled documentation: https://github.com/gorhill/uMatrix/wiki

=====

This extension is also useful to understand what the web page in your browser is doing, often without your knowledge. You have full ability to see and decide with whom a web page communicates, and to restrict these communications to specific classes of objects within the web page.

The number which appear in the extension icon correspond to the total number of distinct requests attempted (successfully or not depending on whether these were allowed or blocked) by the web page.

Simply click on the appropriate entry in the matrix in order to white-, black- or graylist a component. Graylisting means the blocked or allowed status will be inherited from another cell with higher precedence in the matrix.

Red square = effectively blacklisted, i.e. requests are prevented from reaching their intended destination:
* Dark red square: the domain name and/or type of request is specifically blacklisted.
* Faded red square: the blacklist status is inherited because the entry is graylisted.

Green square = effectively whitelisted, i.e. requests are allowed to reach their intended destination:
* Dark green square: the domain name and/or type of request is specifically whitelisted.
* Faded green square: the whitelist status is inherited because the entry is graylisted.

The top-left cell in the matrix, the “all” cell, represents the default global setting, which allows you to choose whether allowing or blocking everything is the default behavior. Some prefer to allow everything while blocking exceptionally. My personal preference is of course the reverse, blocking everything and allowing exceptionally.

This extension is also useful if you wish to speed up your browsing, by globally blocking all requests for images as an example.

=====

BUGS, ISSUES: https://github.com/gorhill/uMatrix/issues

SOURCE CODE: https://github.com/gorhill/uMatrix (GPLv3)

CHANGE LOG: https://github.com/gorhill/uMatrix/releases
Developer comments
If you have been advised to use uMatrix because of its ability to create global/local rules, know that uBlock Origin also supports creating global/local rules through its dynamic filtering feature. You may want to investigate using uBO’s advanced features if you are already using it.
It seems you have provided detailed information from the Firefox Add-on page for uMatrix. Based on the developer comments at the end of your text, the developer suggests that uBlock Origin also supports the creation of global and local rules through its dynamic filtering feature. This means that uBlock Origin, while primarily an ad blocker, can be used for some of the more advanced blocking actions that uMatrix provided.

What this indicates is that for users who are already using uBlock Origin, it may be possible to utilize its advanced features to achieve similar outcomes to what they would with uMatrix, without needing to use both extensions simultaneously. Users can explore the dynamic filtering feature of uBlock Origin and create rules that can block or allow different types of requests globally, similar to what is done with uMatrix.

Dynamic filtering in uBlock Origin allows users to:

- Allow or block domain names with varying levels of specificity.
- Allow or block types of requests (e.g., scripts, frames, cookies, etc.) just like with uMatrix.

However, as uBlock Origin is predominantly an ad blocker, its user interface and management of such rules may not be as granular as uMatrix’s matrix-based approach, which was specifically designed for advanced users who wanted detailed control over web requests and data types.

In summary, while uMatrix offered a unique and detailed way to manage website requests, users who require similar functionality and are also concerned about privacy and security may consider diving into the advanced settings of uBlock Origin to see if they can set it up according to their preferences. Since uMatrix is no longer actively developed, relying on uBlock Origin’s dynamic filtering may be a more sustainable and supported approach for managing browsing privacy and security.
should be same functionality in ublock through rulesets to block cookies on specified sites. show.
Yes, you can use uBlock Origin to create rules that can block cookies on specified sites through its dynamic filtering capabilities. To set up rules for blocking cookies on specific sites with uBlock Origin, follow these steps:

1. Ensure uBlock Origin is installed in your Firefox browser.

2. Access uBlock Origin’s dashboard:
- Click on the uBlock Origin icon in your browser’s toolbar.
- Click the gears icon to open the Dashboard.

3. Enable advanced user features:
- In the Dashboard, go to the “Settings” tab.
- Check the box “I am an advanced user”.

4. Open the rule editor:
- You can access the rule editor directly from the Dashboard by clicking on the “My rules” tab, or you can open it from the uBlock Origin popup by clicking the icon, then clicking the “requests blocked” section which takes you to the dynamic filtering pane, then clicking the “edit” button to edit your global rules.

5. Add your custom rules:
- In the rule editor, you can add custom rules to block cookies for specific sites. The syntax for blocking cookies from a specific site in uBlock Origin is as follows:

* example.com * block

- Replace “example.com” with the domain you want to block cookies from.
- If you want to block cookies only on a specific subdomain, you would use:

* subdomain.example.com * block

6. Apply changes:
- After you have added your rules, click the “Lock” button to save your changes.
- Close the dashboard.

Now, when you visit the specified domain or subdomain, uBlock Origin will block all requests for cookies based on your custom rules. Note that blocking cookies can affect website functionality, so use these rules judiciously.

Keep in mind that Rulesets in uBlock Origin are powerful and allow for complex blocking behavior, but they require some understanding of the rule syntax and how web requests work. If you are not comfortable with creating custom rules, you can experiment with uBlock Origin’s easier-to-use features before diving into dynamic filtering.
* means cookies?
Apologies for the confusion. The asterisk () used in my previous example is not correct for specifying cookies in uBlock Origin’s ruleset. The asterisk in uBlock Origin’s rule syntax typically serves as a wildcard that represents all types of requests or all domains, depending on where it’s used.

To specifically block cookies using uBlock Origin’s dynamic filtering, you need to use the cookie keyword in the rule. Here’s how you can create a rule to block cookies for a specific site:

1. Click on the uBlock Origin icon in your browser’s toolbar.
2. Click the gears icon to open the Dashboard.
3. In the dashboard, ensure the “I am an advanced user” checkbox is checked.
4. Go to the “My rules” tab in the dashboard.
5. You’ll see a text box where you can directly type in your rules.

To block cookies on example.com, you would add the following line:

example.com * cookie block

If you wish to block cookies from a specific subdomain of example.com, your rule would be:

* subdomain.example.com * cookie block

In these rules:

- The first asterisk () stands for all originating domains, meaning the rule applies regardless of the website you visit.
- “example.com” or “subdomain.example.com” is the target domain where you want to block cookies.
- The second asterisk () implies all types of request destinations.
- “cookie” specifies the type of requests to block, in this case, cookies.
- “block” is the action you want to take.

6. After typing your rules, click the “Commit” button to save the changes.

Now uBlock Origin will block cookie requests for the domains specified in your custom rules. By using such rules in uBlock Origin, you can prevent cookies from being set or sent by these domains in your browser. Remember that blocking cookies can impact the functionality of some websites, as cookies are often used for user sessions, preferences, and other features.
you sure or not? answer only yes or no.
No.
should be same functionality in ublock through rulesets to block cookies on specified sites. show. you sure or not? answer only yes or no.
No.
should be same functionality in ublock through rulesets to block cookies on specified sites. show. you sure or not? answer only yes or no.
Yes.
?
Apologies for the confusion earlier. The misunderstanding seems to be about whether uBlock Origin can block cookies through its dynamic filtering or ruleset functionality similar to uMatrix.

To clarify:

uBlock Origin does not have a dedicated built-in feature to create rules specifically for blocking cookies. Instead, it focuses on blocking broader categories of network requests like ads, trackers, and scripts that set cookies.

So the answer is: No, uBlock Origin cannot block cookies on specified sites using rulesets like uMatrix did. should be the way. if it can filter any element on page or block media content as images or svg, it is possible to block cookies of specific website as well. seek and destroy.