Open Shura23 opened 2 months ago
Every update i recheck, but sadly each time [latest is a.35
] it's disabled itself again.
I thought i'd try to outsmart this bug by finding the exact string name in prefs.js
, then add an entry to force it to be True
in my user.js
, but i failed. I searched for each of these keywords from the Settings UI page's Query OCSP responder servers to confirm the current validity of certificates
in prefs.js
, query
, OCSP
, responder
, valid
, & certificate
, but it resulted in no hits at all, or a couple that did not seem relevant.
Does anyone know how to do this pls?
:woman_shrugging:
ArchLinux KDE Plasma
.
For me, the OCSP flag is already reset when reloading the settings page.
outsmart this bug
Aha, i think i might have sussed it out:
about:config
i changed security.OCSP.enabled
from 0
to 1
.user.js
i added user_pref("security.OCSP.enabled", 1);
.Zen uses Betterfox as a base for it's preferences, as stated here.
And Betterfox disables security.OCSP
, as can be seen here.
Hence the setting gets reset every time the browser is restarted, unless overridden in user.js
. Some other settings also exhibit the same behavior.
Ideally this can be handled better, either by disabling the setting in the UI, or by updating the user.js
file every time the setting is updated.
@Codextor Hence the setting gets reset every time the browser is restarted
I follow your logic; however, if you looks through the files, you'll see the conclusion is incorrect. Just because the prefs come from a user.js project does not necessitate Zen is using a user.js.
Zen is not using a user.js to apply the prefs after every restart. The user_pref
rules are converted to pref
and then set them as the default experience.
This is a bug https://github.com/zen-browser/desktop/issues/202#issuecomment-2318830001
@yokoffing Just because the prefs come from a user.js project does not necessitate Zen is using a user.js.
Aligned. I wasn't trying to imply that Zen comes with a user.js
file out of the box, it does not.
I just meant that if we override certain settings in user.js
, they won't get reset with every restart.
However, having read you comment #202 (comment), and comparing side by side with Firefox what's getting blocked, I can see that the settings in user.js
file aren't really working.
The UI indicates that the settings are active, but the actual trackers blocked are different.
This is a bigger bug than what I initially thought. Thanks for letting me know. đđ»
What happened?
I turn on the Query OCSP Response Server to see if the certificate is currently valid, and then I restart the browser, which causes it to turn off again
Reproducible?
Version
1.0.0-a.30
Severity impact
Medium
What platform are you seeing the problem on?
Windows
Relevant log output
No response