Cookie Manager replacement Topic is solved

[hujan86]

Is there an extension that can be a full replacement for PM & Basilisk's built-in cookie manager? I'm hoping for something that can export and import a list of blocked/allowed cookies in a simple text file format.

[doofy]

Does this give you roughly what you want?

https://addons.mozilla.org/en-US/firefo ... ager-plus/

[coffeebreak]

A couple of other possibilities might be Cookiekeeper or Cookie Controller.

Cookiekeeper ex/imports either cookies or exceptions list in choice of .json or .csv.
Cookie Controller ex/imports combined settings+exceptions list as .xml.

[dark_moon]

Cookies Exterminator from JustOff

[hujan86]

I imported the exception list from PM using Cookie Controller. When I checked the exception list in Basilisk, the browser has added "http://" at the front of every address. In this case, is it necessary to add *, so it becomes something like "http://*.ads.com" in order to make the cookie block affective in Basilisk?

[coffeebreak]

I imported the exception list from PM using Cookie Controller. When I checked the exception list in Basilisk, the browser has added "http://" at the front of every address.

Pale Moon and Basilisk don't handle cookie permissions exactly the same.

Basilisk uses the same system as FF 42 + later that requires each permission to be entered separately for http and https versions of a domain (and requires the full address to be written out: https:// example.org, http:// example.org).
Cookie Controller [CC] apparently treats Pale Moon's cookie permissions as http-only when importing between these two systems.
(And for info, the same issue is present with Cookiekeeper.)

For importing, there are a couple of ways around this...

1. The easiest is probably to copy the file permissions.sqlite from your Pale Moon profile to Basilisk profile.
(I tried this and it worked just fine despite the browsers' differences: both http* & https* showed up in cookie permissions.)

• Open both browsers. Open their respective profile folders/directories (Help -> Troubleshooting Information -> Show Folder).
• Close both browsers but leave their profile windows/directories open.
• Copy the file over.
  One more thing: permissions.sqlite has all of your permissions (pop-ups etc.). If you don't want to keep the additional permissions from PM...
• Export your now-complete cookie permissions with Cookie Controller, delete permissions.sqlite from your Basilisk profile (it will get re-created), and import the cookie permissions (from the backup you just made) back in with Cookie Controller.

2. It's also possible, if you prefer, to edit either the Cookie Controller (or Cookiekeeper) permissions file (that was exported from PM) with a text editor.

Cookie Controller:
Cookie Controller overwrites current permissions when you import (it does not append), so the one file will need to have all permission entries, http and https.
In addition, CC changed some syntax for the FF/Basilisk system, so that too would need updating.
Example:
An entry that begins with: <exception host='example.com'
Would have to be replaced with two entries that start, respectively, with:
<exception uri='http://example.com/'
and <exception uri='https://example.com/'

Cookiekeeper (for completeness):
CK does not overwrite current permissions when a file is imported (it appends), so it's possible to use more than one file if desired.
Just copy the file and use search/replace to change the http entries -> https.
Import the http & https files independently, or combine the contents into one file. Either way worked for me.
And FWIW, it worked the same whether using json or csv.


Adding new cookie permissions.

is it necessary to add *, so it becomes something like "http://*.ads.com" in order to make the cookie block affective in Basilisk?

AFAIK such a shortcut won't work natively (without using a cookie extension). Basilisk requires full and separate entry for http & https permissions.
Cookie Controller does add both http & https permissions - if you use its permissions menu while on a site's page.
Another extension, Cookie Masters does the same.
Cookiekeeper, unfortunately, does not appear to do this.

[hujan86]

^
If I add the single entry for example "https://xxxmanager.com" , will the cookies from say, "https://ads.xxxmanager.com" get blocked as well? Or do I need to add another specific entry for the latter address as well?

In addition, when I want to always allow a cookie from a site (e.g. bank's website), is the "www" prefix required?

[coffeebreak]

If you add "https://xxxmanager.com", cookies from "https://ads.xxxmanager.com" should get blocked as well.

But cookies from "http://xxxmanager.com" and "http://ads.xxxmanager.com" will not get blocked unless an entry also exists for "http://xxxmanager.com".

If you don't use any cookie extension, you will need to add each of these independently.
But some cookie extensions do enable you to create both entries at the same time.

You can open Basilisk's cookies permissions manager to see if both entries are present.
(Options -> Privacy -> History tab -> "Use custom settings for history" -> click the 'Exceptions...' button)

[hujan86]

If you add "https://xxxmanager.com", cookies from "https://ads.xxxmanager.com" should get blocked as well.

But cookies from "http://xxxmanager.com" and "http://ads.xxxmanager.com" will not get blocked unless an entry also exists for "http://xxxmanager.com".

If you don't use any cookie extension, you will need to add each of these independently.
But some cookie extensions do enable you to create both entries at the same time.

You can open Basilisk's cookies permissions manager to see if both entries are present.
(Options -> Privacy -> History tab -> "Use custom settings for history" -> click the 'Exceptions...' button)

A. "http://xxxmanager.com" & "https://xxxmanager.com"
B. "http://ads.xxxmanager.com" & "https://ads.xxxmanager.com"

I see. So, rule example B is redundant. "http://xxxmanager.com" is the same as "http://*.xxxmanager.com"

[coffeebreak]

So, rule example B is redundant.

Yes it is.

Furthermore, Basilisk's cookie permissions manager does not seem to understand or accept rules with syntax like: "http://*.xxxmanager.com".
I tried adding such a rule and got a weird, malformed, useless result (http://http)...

Tried adding "http://*.xxxmanager.com" to Basilisk cookie exceptions:

This was the result: