7/30/2023 0 Comments Firefox esr 52.8I'll make a note to follow up about the desupport notice then. September does make more sense since we will continue to provide 52.9.x dot releases until then. > easy, but let me double-check with :Rail, maybe I misunderstood the > September when we specifically have this EOL. I thought the Desupport page would come up only in > cover the WNP for xp/vista on esr 52.9.0 today". Fixed: + CVE-2018-6126 Heap buffer overflow rasterizing paths in SVG with Skia Affected Package. JAndrey Cherepanov 60.0.2-alt1 - New ESR version (60.0.2). Cornel Ionce confirmed in IRC "we'll make sure to also Security fix for the ALT Linux 10 package firefox-esr version 60.0.2-alt1 T00:00:00 Description. > 52.9.0esr build2 as well (most recent build). > We've already set that up for 52.9.0esr build1 and that applies for (In reply to Mihai Tabara ⌚️GMT from comment #12) I'll leave the NI info until I reach back later in the day with a confirmed answer. Settting this up Balrog is easy, but let me double-check with :Rail, maybe I misunderstood the mechanics behind the updates rules. I thought the Desupport page would come up only in September when we specifically have this EOL. > Firefox Nightly and Aurora users on XP and Vista last year in bug 1319167. > Windows XP and Vista users on ESR 52.9. > We also want to add a desupport notice (in the "About Firefox" dialog) for Cornel Ionce confirmed in IRC "we'll make sure to also cover the WNP for xp/vista on esr 52.9.0 today". QA confirmed that's working fine in so that should apply for build2 as well. We've already set that up for 52.9.0esr build1 and that applies for 52.9.0esr build2 as well (most recent build). > Linux users updating to ESR 52.9 or ESR 60.x. We do *not* need to show this page to Windows 7/8/10, macOS, or > We want to show this WNP only to Windows XP and Vista users when they update > Here is the list of localized versions of the SUMO page: > Mihai, here is the link to the XP EOL SUMO page: Shame on Mozilla.(In reply to Chris Peterson from comment #11) Honestly, I find these undisclosed, hidden updating processes that appear to be "outside" of user control to simply be insidious and wrong. I even noticed entries, and one entry might have been a timer, that track when Firefox was last updated, so I suspect they have to do with Firefox's built-in update mechanisms that are buried in Mozilla's source code. I even took the drastic step of removing the app update URLs that are buried in "about:config". Perhaps this "update timebomb" is buried in the Mozilla source code or controlled by something in "about:config" that simply ignores what is set on the "Options->Advanced->Updates" page.įurther update: I have dug around in "about:config" and found various references to updating the app that were enabled, so I disabled them. I can clearly see that "Options->Advanced->Update" then the "Firefox updates" section on that page is flagged as "Never check". Update: I have checked my backup Firefox Portable 52.8.1 ESR install, the "source" of my "working" FF Portable 52.8.1 ESR setup. That's one of the biggest positives to using Portable Apps. Haller are you there?Īt least I keep a backup copy of my original Firefox Portable 52.8.1 ESR installation. Is there any hope that the Portable App developers can answer why their packaging is trying to and eventually updates itself from Mozilla? If I can't see the screen clearly I cannot use Firefox. Why do I stay on Firefox Portable 52.8.1 ESR? I have some "legacy" addons that I need to use to see the screen that have not yet been updated to Mozilla's new addon standards. Solution Upgrade to Mozilla Firefox ESR version 52.8 or later. It is, therefore, affected by multiple critical and high severity vulnerabilities. I thought the Portable Apps developers disabled all automatic updating features of the Portable Apps that they package simply because updated binaries from the original developers would/could conflict or crash the skillful packaging work done by the Portable Apps developers. The version of Mozilla Firefox ESR installed on the remote Windows host is prior to 52.8. Firefox Portable 52.8.1 ESR will periodically crash until the background updating is completed. When Firefox Portable 52.8.1 does finish it's updating it crashes, forcing a restart of the app and loss of all of my work I just lost GIGABYTES of queued (using DownThemAll, but without saving the filenames in the queue) file downloads thanks to this unwanted, unexpected, and "timebombed" update behavior. At least that's what I seem to remember from when it last bombed out the main FF 52.8.1 ESR folder timestamp is about 40 days old right now. I think the "timebomb" kicks off every 30 to 60 days. Somehow Firefox Portable ESR is automatically updating itself. My current installed version of Firefox Portable 52.8.1 ESR loads up and reports as Firefox Portable 60.0.10 ESR.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |