Am 20.03.2012 13:50, schrieb Adi Kriegisch:
> Hi!
>
[...]
>> Are there any other settings to be done?
> You probably added the directive to the wrong place, then? Forced
> preferences should go to chrome/defaults/preferences/site.js
> You could add some more prefs to get automatic updates and TB updates as
> well (but most of them are the default anyways):
> || force_bool_pref("extensions.update.auto", true);
> || force_bool_pref("extensions.update.enabled", true);
> || force_bool_pref("app.update.silent", true);
> || force_bool_pref("app.update.enabled", true);
> || force_bool_pref("app.update.auto", true);
> || force_int_pref("app.update.mode", 1);
>
> Hope, this helps.
Thanks, this helped a lot but I still had the same "not builtin"
problem. After analysing the source code from thunderbird sources I
finally found two additional settings. now I have
force_bool_pref("app.update.cert.requireBuiltIn", false);
force_bool_pref("extensions.install.requireBuiltInCerts", false);
force_bool_pref("extensions.update.requireBuiltInCerts", false);
in my custom-preferences.js file (want to run it every thunderbird
start). the extension.update did not the trick, but extension.install
did. Now thunderbird 10esr is able to automatically update sogo and
lightning extensions from my private server.
>
> Ah, and one more thing: intermediate(*) CAs need to be either in TB cert store
> or in the cert chain the web server presents to the client...
>
> -- Adi
>
> (*) just in case you're using a root ca that issued a web server ca that
> is used to sign server certificates. But if you're running your own pki
> you most probably know what you're doing... ;-)
I don't know enough here. I have set up some ssl servers with my own CA
but as I use it for my family only I only use one root certificate. So
there is no chain involved. This is more a test and play environment.
Martin
--
[email protected]
https://inverse.ca/sogo/lists
