Skip to content

Conversation

@goodusername123
Copy link
Contributor

Same principle as #3269
The string matching is checking against exact strings and the signature's letter casing was changed causing this issue to reappear. I don't know if the old letter casing for the signature is officially retired or is subject to return at any point (I'm unfamiliar with the process around acquiring or managing digital signatures), but If you don't plan on ever using the old letter casing for signing again then it's probably better to just replace the old BrowserWorks string check with the new string rather then adding a whole new check on-top like I've done here.

MrAlex94 and others added 30 commits November 3, 2025 16:04
Also includes:

* feat: improve support for bootstrapped extensions
Added support for custom preference pages.
* fix: incorrect loading order for bootstrap loader
* fix: BootstrapLoader

(cherry picked from commit eb40811)
(cherry picked from commit 406d531)
(cherry picked from commit 15940da)
(cherry picked from commit 02227c4)
…tions update method to handle missing updateInstall
(cherry picked from commit d97ab04)
(cherry picked from commit 9a06eb5)
(cherry picked from commit b10ab25)
black7375 and others added 25 commits November 6, 2025 14:13
(cherry picked from commit f0a5ff1)
(cherry picked from commit 88fb86b)
(cherry picked from commit 4f892e0)
The string matching is checking against exact strings and the signature's letter casing was changed. This commit fixes `about:third-party` not trusting any of Waterfox's DLL files.
@MrAlex94 MrAlex94 force-pushed the current branch 3 times, most recently from 7d8f658 to c7662e5 Compare November 25, 2025 16:00
@MrAlex94
Copy link
Collaborator

Thanks, squashed into 2a74b9a

@MrAlex94 MrAlex94 closed this Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

6 participants