Overclock.net - An Overclocking Community - Reply to Topic

Thread: [Engadget] Firefox disabled all add-ons because a certificate expired (updated) Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
05-20-2019 12:09 PM
ThrashZone Hi,
Anyone lost faith in forefox updates now lol
Sitting on 66.0.4 and update 66.0.5 is waiting
05-07-2019 07:56 AM
JackCY
Quote: Originally Posted by ltpdttcdft View Post
On the Windows mainstream version, the xpinstall.signatures.required option (and many others too) does nothing. It's compiled that way. Only ESR and development versions work.

Works fine on most Linux versions compiled by packagers.
Exactly. It only works on some variants. People forget that FF has many versions and variants. You can't disable signatures on all and why should you, that's not the issue, the certificate is.
Not everything you can change in config has an effect on all variants and versions. Same with not all variants and versions are "fixed" by Mozilla.
05-07-2019 12:22 AM
Elrick
Quote: Originally Posted by Ashura View Post
Thank you!. I was expecting it to auto update, don't know what it was waiting for.

Maybe it's waiting for you, to get a better Operating System .
05-06-2019 07:43 PM
Ashura
Quote: Originally Posted by Drake87 View Post
I had to manually check for an update, then it updated and fixed itself. Usually, it keeps updated automatically.
Thank you!. I was expecting it to auto update, don't know what it was waiting for.
05-06-2019 05:16 PM
Drake87 I had to manually check for an update, then it updated and fixed itself. Usually, it keeps updated automatically.
05-06-2019 04:57 PM
Diffident
Quote: Originally Posted by ltpdttcdft View Post
On the Windows mainstream version, the xpinstall.signatures.required option (and many others too) does nothing. It's compiled that way. Only ESR and development versions work.

Works fine on most Linux versions compiled by packagers.

I guess that's why, since I'm a Linux user. Linux FTW!
05-06-2019 04:49 PM
ltpdttcdft
Quote: Originally Posted by Diffident View Post
What version of Firefox doesn't allow access to about:config? Every version of firefox I've used for at least the past 10 years will bring up a settings page when typing about:config in the address bar.

There is also:
Code:
  • about:support
  • about:buildconfig
  • about:memory
  • about:performance
  • about:serviceworkers
  • about:profiles
I'm using the standard 66.0.3 release.
On the Windows mainstream version, the xpinstall.signatures.required option (and many others too) does nothing. It's compiled that way. Only ESR and development versions work.

Works fine on most Linux versions compiled by packagers.
05-06-2019 04:19 PM
Diffident
Quote: Originally Posted by JackCY View Post
Which only works for some versions of FF.



Because not every FF has studies. The solution I've linked works on old FF too and is based on the file/patch you linked. Mozilla simply hasn't provided a solution yet, if ever, to apply it to older FF so users have to do so on their own.

What version of Firefox doesn't allow access to about:config? Every version of firefox I've used for at least the past 10 years will bring up a settings page when typing about:config in the address bar.

There is also:
Code:
  • about:support
  • about:buildconfig
  • about:memory
  • about:performance
  • about:serviceworkers
  • about:profiles
I'm using the standard 66.0.3 release.
05-06-2019 02:26 PM
JackCY
Quote: Originally Posted by sticks435 View Post
My fix isn't the studies fix, it's the actual .XPI file.
Someone else can test that on older FF. Installing it made no change on mine, nor uninstalling it, I already have the certificate from it installed in FF. It did not seem to add a new cert. only appeared as an addon, which is very weird solution to this problem. "Broken addons! Lets add another addon!"
05-06-2019 10:32 AM
epic1337 FF v66.0.4 doesn't have this issue, so far all my add-ons works.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off