Deploy preset whitelist for new profile

[klaus.uhr]

Noscript 10.1.6.4 on Firefox 58.0.1

We use Firefox and NoScript in the enterprise and deploy a number of presets with the CCK (Customization Kit from Mike Kaply) using the auto config mechanism of Mozilla. We include also a predefined whitelist containing some of our business webpages. Thus these pages are already trusted when a user opens Firefox with a new profile. The setting in question is "capability.policy.maonoscript.sites". We had never a problem with it until the arrival of Firefox Quantum and NoScript 10.x.

Now as for the whitelist this mechanism is broken. Even though the whitelisted domains are shown in about:config, NoScript does not import them nor take them into account. They are not contained in storage-sync.sqlite where we find the presets of NoScript. Sure we could export this whitelist and let the user import it by himself. But it this troublesome as the user is already confronted with a scrambled enterprise welcome page the first time she/he opens Firefox until she/he trusts them in Nocript. We would like to know if there is a method to let NoScript itself import the domains stored in "capability.policy.maonoscript.sites" the first time a new profile is launched. (I don't speak of existing profiles because theirs whitelist is adopted.)

Thanks for any idea to circumvent the actual limitation.

Klaus

[Pansa]

The whitelist is afaik currently saved in storage-sync.sqlite in the firefox profile folder.

So maybe it is possible to dump a preconfigured one after creating the profile or running a script that inserts the whitelist into the sql database?

[barbaz]

Removed the email address. We don't give email support, but this being a public forum there are surely bad bots looking to harvest email addresses for spamming and other nefarious purposes.

This sounds like a CCK question, not a NoScript question. I suggest you ask the CCK folks.

[klaus.uhr]

Thanks to both of you for the comments. - Regarding this suggestion:

So maybe it is possible to dump a preconfigured one after creating the profile or running a script that inserts the whitelist into the sql database?

The problem with this approach is that when Firefox is installed there is no profile yet. And at the time when (with the first launch of Firefox by the user) a new profile is created, there is no instance to run a script, unless we had a listener process which would sit in memory and respond to "on creation of Firefox profile do..." with the scripted action.

Alas, so I will turn to Mike Kaply, he developer of he CCK, as proposed by barbaz. Thanks also for hiding the email address.

Klaus