1551321 - Please fix the certificate problem with Firefox 48.0.2 which is the last to run on Mac 10.6.8 Thanks,

Status: RESOLVED FIXED

(Firefox :: Untriaged, defect)

Description

[p123v]

Attachment: Gram_Bug.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:48.0) Gecko/20100101 Firefox/48.0

Steps to reproduce:

Nothing

The certificate timeout or died by itself

Actual results:

Grammarly for Firefox add-0n has been disabled due to a certificate issue.

Can not update any further with Firefox as 48.0.2 is the last to run on Mac 10.6.8 which my system is maxed at.

Expected results:

A patch for 48.0.2 for Mac to fix this problem similar to the patch that has been issued for FireFox 66.0.4 and 66.0.5

Many of us are stuck on the older version (48.0.2) of Firefox due to system limitations

Comment 1

[Robert Helmer [:rhelmer]]

Could you possibly try with an unbranded build, using one of the attachments (most likely the one labeled "52 to 57") from bug 1550793 ?

You can find unbranded 48 builds at: https://wiki.mozilla.org/index.php?title=Add-ons/Extension_Signing&oldid=1142565

These should allow signatures to be disabled, you'll likely need to modify the install.rdf to set the minimum version.

Thanks!

Comment 2

[[:philipp]]

another alternative would be switching to firefox 45esr where you can still disable addon signature checks by setting xpinstall.signatures.required to false in about:config:
https://archive.mozilla.org/pub/firefox/releases/45.9.0esr/mac/

Comment 3

[smayer97]

What is an unbranded build and what does it do?

What would need to be changed in install.rdf? Do not know enough but do need a solution for v48.0.2 for Mac for same reason.

Comment 4

[Robert Helmer [:rhelmer]]

I actually went ahead and tested this on 47, had to make a few minor changes so I don't think you need to bother testing, thanks for the response though!

I'll post the XPI momentarily but here are answers to your questions:

(In reply to smayer97 from comment #3)

What is an unbranded build and what does it do?

It's a Firefox build that's equivalent to the regular release, but doesn't contain Firefox branding (logo, etc) and signing can be disabled.

What would need to be changed in install.rdf? Do not know enough but do need a solution for v48.0.2 for Mac for same reason.

I think you'd want to modify this line:

<em:minVersion>57</em:minVersion>

To be instead:

<em:minVersion>*</em:minVersion>

However as I noted above, there are a few changes that need to be made so I'll just upload the hotfix.

Comment 5

[Robert Helmer [:rhelmer]]

Attachment: Hotfix with no minimum version

Comment 6

[Robert Helmer [:rhelmer]]

Comment on attachment 9064660 [details]
Hotfix with no minimum version

Could you please test this hotfix extension? You shouldn't need an unbranded build, instead:

1. download this XPI file
2. open about:debugging
3. click "Load Temporary Add-on" button
4. select XPI file you downloaded

This should apply the fix and get your extensions going again.
If you open the Browser Console, you should see output like:

new intermediate certificate added bootstrap.js:39
signatures re-verified bootstrap.js:61

If this works I expect it to permanently fix your profile, when you restart Firefox next the hotfix will be uninstalled and you shouldn't need to install it again.

Comment 7

[smayer97]

Thanks for the quick reply. I'll definitely give this a try. Just to be clear, I have a few follow-up questions:

1. are the changes still needed to install.rdf with this updated XPI Hotfix?
2. Are there any risks or precautions to consider before applying this if it fails?

Thanks kindly.

Comment 8

[Robert Helmer [:rhelmer]]

(In reply to smayer97 from comment #7)

Thanks for the quick reply. I'll definitely give this a try. Just to be clear, I have a few follow-up questions:

1. are the changes still needed to install.rdf with this updated XPI Hotfix?

No, I went ahead and modified it in the latest attachment. It should not require any further adjustment

2. Are there any risks or precautions to consider before applying this if it fails?

This is essentially the same as the other hotfixes, but we don't have the QA bandwidth to test releases earlier than 52 right now so it is at your own risk.

I would suggest backing up your profile (in general, and also right before testing things like this :) )

Thanks kindly.

Comment 9

[jscher2000]

Re: disabled_add_on_fix_for_firefox_52_56-1.1.4.xpi
at: https://addons.mozilla.org/firefox/addon/disabled-add-on-fix-52-56/

On AMO, the title was updated to Disabled Add-on Fix for Firefox 47 - 56 when version 1.1.4 was made available.

So is this bug fixed?

Comment 10

[:shell escalante]

The Firefox 47-56 extension fix on AMO has not been widely tested on pre-52 versions of Firefox, but has been reported to work on some machines. https://addons.mozilla.org/en-US/firefox/addon/disabled-add-on-fix-52-56/

Comment 8 has more details.